[INFRA-5852] Handle CronJob upgrade via active Job Pod deletion#1
Merged
[INFRA-5852] Handle CronJob upgrade via active Job Pod deletion#1
Conversation
Instead of immediately creating new Jobs we will instead delete pods belonging to active Jobs. This will cause the job controller to re-create the pods based on the defined policies. As such we will not violate the CronJob schedule, suspension and concurrency policies.
sazap10
approved these changes
Mar 25, 2026
trvrnrth
changed the title
trvrnrth
added a commit
that referenced
this pull request
Mar 25, 2026
Instead of immediately creating new Jobs we will instead delete pods belonging to active Jobs. This will cause the job controller to re-create the pods based on the defined policies. As such we will not violate the CronJob schedule, suspension and concurrency policies.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Instead of immediately creating new Jobs we will instead delete pods belonging to active Jobs. This will cause the job controller to re-create the pods based on the defined policies.
As such we will not violate the CronJob schedule, suspension and concurrency policies.
Note: This also exists as an upstream PR at stakater#1098