stakater
[BUG] Reloader starting jobs based on paused CronJobs
We have a globally enabled Reloader, this worked fine for a while but we recently found a dangerous edge case.
When a paused cronjob would create a job that mounts a configmap, if the configmap changes an instance of the job is created. This instance is created outside of the cronjob mechanism with no way to track why it was created, too.
Expected behavior A paused cronjob should not be instantiated under any circumstance
Additional context I would like a way to enable Reloader globally but ignore cronjobs, even if not paused. This behavior is highly dangerous, as I would guess most cronjobs are not supposed to run outside of their schedule at all.
What version is this occurring from? It started occurring when I recently upgraded my version from v0.0.113 to v1.2.1. We would like to revert back to a version where the problem does not occur.
