fix: Make sure that StatusUpdateTrigger and InfoUpdateTrigger keep running on rolling updates - #5663
Open
cdprete wants to merge 1 commit into
Open
fix: Make sure that StatusUpdateTrigger and InfoUpdateTrigger keep running on rolling updates#5663cdprete wants to merge 1 commit into
cdprete wants to merge 1 commit into
Conversation
running on rolling updates
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
1 participant
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.
Fixes #5450 (comment).
Better titles are welcome :D
If approved and merged, it would be great to have this released as soon as possible.
I'm currently running in DEV with a patched local version (the one in this PR) and in QA&PROD I had to destroy and recreate the deployment to re-trigger the fetching of the instances, therefore those envs are good until one Pod dies or if I've to redeploy something.