-
Notifications
You must be signed in to change notification settings - Fork 336
Helm chart: Support providing RollingUpdate maxSurge and maxUnavailab… #5665
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
Changes from 3 commits
af7e621
1e6da59
cc76906
2c9b329
643e2e8
8fba8e3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| ### Support providing RollingUpdate maxSurge and maxUnavailable values ([Issue #5664](https://github.com/apollographql/router/issues/5664)) | ||
|
|
||
| RollingUpdate maxSurge and maxUnavailable are commonly used deployment configuration values. This change makes their | ||
| values able to be set via the router helm chart. | ||
|
|
||
| By [Jon Christiansen](https://github.com/theJC) in https://github.com/apollographql/router/pull/5665 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -218,6 +218,15 @@ autoscaling: | |
| # type: cpu | ||
| # targetUtilizationPercentage: 75 | ||
|
|
||
|
|
||
| rollingUpdate: | ||
| {} | ||
| # Adjust rolling update strategy. Can take absolute values or % values. | ||
| # (https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment) | ||
| # Defaults if not set are: | ||
| # maxUnavailable: 25% | ||
| # maxSurge: 25% | ||
|
|
||
|
Comment on lines
+222
to
+230
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would be nice to have line 224 moved to line 221 and specified as a helm-docs style comment
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I've adjusted and used helm-doc style comment per your feedback.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @garypen - are you good with this PR now with the adjustment made?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @garypen or @BrynCooke -- Sorry for the harassment, but can we get this merged in. I have at least one more PR I'd like to submit, but I'd like this one settled first before I do so.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @theJC Sorry about the delay, I've been on vacation. |
||
| nodeSelector: {} | ||
|
|
||
| tolerations: [] | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.