-
Notifications
You must be signed in to change notification settings - Fork 880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completed Event/Condition should only trigger during updates #2103
Comments
To fix this, I think the existing argo-rollouts/utils/conditions/conditions.go Lines 257 to 286 in 03636ab
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Currently, we equate the Completed condition to a Healthy rollout. However, a Rollout becomes Progressing for other reasons than an update (e.g. pod restarts).
Looking at the intent of the condition, it is intended to only emit when updates complete. See:
The Completed condition should only be set to False in the middle of an update and set to True at the end of the update. A good way to detect this is simply comparing current and stable pod hashes:
Diagnostics
What version of Argo Rollouts are you running? v1.2.0
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: