We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The canary strategy is supposed to behave like a Deployment rollingUpdate strategy by defaulting both maxUnavailable and maxSurge to 25%.
While maxSurge does seem to be defaulting to 25%, maxUnavailable appears to be defaulting to 0.
What version of Argo Rollouts are you running?
v0.10.2 but I tested with v0.8.2 and v0.6.3 those versions also exhibit the same behavior.
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:
@dthomson25 helped me pinpoint the bug to here:
c8d7de4#diff-460e0448455cae92ce052a3a2d029eb1e38a2c1d9c29c994e5128cae2a7e44c9R17
Sorry, something went wrong.
khhirani
Successfully merging a pull request may close this issue.
Summary
The canary strategy is supposed to behave like a Deployment rollingUpdate strategy by defaulting both maxUnavailable and maxSurge to 25%.
While maxSurge does seem to be defaulting to 25%, maxUnavailable appears to be defaulting to 0.
Diagnostics
What version of Argo Rollouts are you running?
v0.10.2 but I tested with v0.8.2 and v0.6.3 those versions also exhibit the same behavior.
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: