[Feature] New updateScheduleCronTabs annotation #814
Conversation
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
|
Hey! Great feature here. Thanks @david-garcia-garcia ! Is there any chance we can push this forward? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a new Keel annotation :
The annotation can contain more than one schedule configuration separated by comas, each configuration consists of a cron and a window size. I.e. 0 0 3 * * 0|60m the resource will be updated between 3 and 4 A.M every sunday.
For this to work make sure that the pollSchedule frequency for that image is less than the resource update window.
The purpose of this is to circunvent current limitations regarding control on when images are effective applied to K8S resources. The existing /pollSchedule annotation is aimed at controlling watchers image polling. Because watchers are shared, you have little control on when images are effectively deployed.
This opens the door to new use cases, i.e. having update rings.