<p>When my ConfigMap changes, I'd like my CronJob to restart.</p>
<p>There's a trick in Helm to make this happen for Deployments using an annotation that contains the SHA of the ConfigMap (see <a href="https://stackoverflow.com/a/61469357/2223706">here</a> or <a href="https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments" rel="nofollow noreferrer">here</a>).</p>
<p>This works for my Deployment, doing <code>kubectl get deployments</code> show the AGE is just a couple minutes.</p>
<p>But not my CronJob, doing <code>kubectl get cronjobs</code>, the &quot;AGE&quot; is still hours old implying they haven't restarted.</p>

Garrett
<p>So, it turns out CronJobs don't need to be restarted when the ConfigMap changes anyway.  Everytime a Job is created, the Pod that spins up to execute the Job seems to use the latest ConfigMap values anyway.</p>
