-
Notifications
You must be signed in to change notification settings - Fork 988
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
Add support for max_surge #2630
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All in all, looks good. I have left a few comments. Feel free to ping me if you have any questions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks!
Optional: true, | ||
Default: 1, | ||
ValidateFunc: validation.StringMatch(regexp.MustCompile(`^([1-9][0-9]*|[1-9][0-9]%|[1-9]%|100%)$`), ""), | ||
ValidateFunc: validation.StringMatch(regexp.MustCompile(`^(0|[1-9][0-9]*|[1-9][0-9]%|100%)$`), ""), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this crashes and burns if you set anything from "1%" to "9%". At least it fails on 1% for us:
│ Error: expected value of spec.0.strategy.0.rolling_update.0.max_unavailable to match regular expression "^(0|[1-9][0-9]*|[1-9][0-9]%|100%)$", got 1%
Description
PR fixes #2609
Acceptance tests
Output from acceptance testing:
Release Note
Release note for CHANGELOG:
References
Community Note