<p>I'm thinking of a solution to do a rolling update on a schedule without really releasing something. I was thinking of an ENV variable change through kubectl patch to kick off the update in GKE.</p>
<p>The context is we have containers that don't do garbage collection, and the temporary fix and easiest path forward and is cycling out pods frequently that we can schedule on a nightly.</p>
<p>Our naive approach would be to schedule this through our build pipeline, but seems like there's a lot of moving parts.</p>
<p>I haven't looked at Cloud Functions, but I'm sure there's an API that could do this and I'm leaning towards automating this with Cloud Functions.</p>
<p>Or is there already a GKE solution to do this?</p>
<p>Any other approaches to this problem?</p>
<p>I know AWS's ec2 has this feature for ASG, I was looking for the same thing so I don't to do a hacky ENV var change on manifest.</p>

edmamerto
<p>I can think of two possibilities:</p>
<ul>
<li><a href="https://cloud.google.com/kubernetes-engine/docs/how-to/cronjobs" rel="nofollow noreferrer">Cronjobs</a>. You can use CronJobs to run tasks at a specific time or interval. Suggested for  automatic tasks, such as backups, reporting, sending emails, or cleanup tasks. More details <a href="https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/" rel="nofollow noreferrer">here</a>.</li>
<li><a href="https://cloud.google.com/kubernetes-engine/docs/how-to/automated-deployment" rel="nofollow noreferrer">CI/CD with CloudBuild</a>. When you push a change to your repository, Cloud Build automatically builds and deploys the container to your GKE cluster.</li>
</ul>
