Helm chart: Support providing RollingUpdate maxSurge and maxUnavailab…#5665
Helm chart: Support providing RollingUpdate maxSurge and maxUnavailab…#5665garypen merged 6 commits intoapollographql:devfrom
Conversation
Add suggested change per PR comments Co-authored-by: Nishchal Gautam <cyberhck@users.noreply.github.com>
|
CI performance tests
|
BrynCooke
left a comment
There was a problem hiding this comment.
Looks good but needs helm/chart/router/README.md updating.
| 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% | ||
|
|
There was a problem hiding this comment.
Would be nice to have line 224 moved to line 221 and specified as a helm-docs style comment
There was a problem hiding this comment.
I've adjusted and used helm-doc style comment per your feedback.
There was a problem hiding this comment.
@garypen - are you good with this PR now with the adjustment made?
There was a problem hiding this comment.
@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.
There was a problem hiding this comment.
@theJC Sorry about the delay, I've been on vacation.
…le values
RollingUpdate maxSurge and maxUnavailable are commonly used deployment configuration values. This change makes their values able to be set via the router helm chart.
Fixes #5664
Checklist
Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.
Exceptions
Note any exceptions here
Notes
Footnotes
It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩
Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩
Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩