fix: requeue if failed to trigger an un-instrument rollout #2406
Conversation
This file contains 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
blumamir
approved these changes
Feb 8, 2025
| kubectl rollout status deployment -l app=inventory | ||
| kubectl rollout status deployment -l app=pricing | ||
| kubectl rollout status deployment -l app=membership | ||
| content: ./wait_for_rollout.sh |
There was a problem hiding this comment.
at this point, we don't yet know if the rollout has started or not, right?
can it lead to race conditions?
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.
sourcese2e test by waiting 1 second between rollouts. This cause flakiness since we are now using a timestamp annotation to trigger a rollout. This timestamp has a resolution of seconds, hence if the test progresses through 2 steps in less than a second we'll have a missing rollout.