-
Notifications
You must be signed in to change notification settings - Fork 75
Add PodDisruptionBudget
to helm chart
#517
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
Conversation
Hi @frauniki. Thanks for your PR. I'm waiting for a cert-manager member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@erikgb @wallrj @SgtCoDFish |
/ok-to-test |
…nhance application availability during maintenance feat(values.schema.json): extend schema to include podDisruptionBudget properties for better validation chore(values.yaml): add default podDisruptionBudget configuration with examples for user guidance Signed-off-by: frauniki <[email protected]>
…ion to provide users with guidance on setting disruption budgets Signed-off-by: frauniki <[email protected]>
/cc @hawksight |
Signed-off-by: frauniki <[email protected]>
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.
Hey @frauniki, thank you for noticing the pdb isn't present in the chart. Really appreciate the PR to get this in place.
I would however like to consider if you could make the values and configuration match the pattern used by cert-manager and trust-manager, so that we have a consistent configuration approach where possible.
Basically, this would mean:
- adding an
enabled
key defaulting tofalse
- consistent with your default - having config keys for both
minAvailable
&maxUnavailable
as doscumented propertirs. - Copy the login in the other charts to prevent a user configuring both and getting a k8s error further down the stack, eg: https://github.com/cert-manager/cert-manager/blob/master/deploy/charts/cert-manager/templates/poddisruptionbudget.yaml#L20-L28
Let me know if that makes sense or you have other reasons to keep it as it, I think it's a trade off but I'd go towards consistency where it makes sense.
…ager pattern Signed-off-by: frauniki <[email protected]>
@hawksight |
/retest |
- Set default - Leave unset (documented only) - Regenerate README and values schema to match This keeps templates simple (with-blocks) and lints clean. Signed-off-by: frauniki <[email protected]>
/lgtm I think in the current state it's safe to merge. People have to opt into this, at which point they should make their own choice about what setting is best for their installation. Thank you @ajvn for the lengthy input on this topic too for getting a good default. At this point we diverge from cert-manager docs, but I think we can revisit that if important later on. |
@hawksight: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
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 can't approve, so back to maybe @erikgb?
I will review this later today or tomorrow. The generated Helm docs can be improved, I think, but I need to find out exactly how. Maybe @frauniki can take a look at https://github.com/cert-manager/helm-tool? |
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 just added some suggestions that I hope will fix the Helm docs and schema.
Signed-off-by: frauniki <[email protected]>
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.
Thanks a lot, @frauniki. Especially for the last-minute adjustments. 🚀
/label tide/merge-method-squash
/lgtm
/approve
@erikgb: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: erikgb, hawksight The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/label tide/squash |
@erikgb: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
fixed Add PodDisruptionBudget to helm chart #516
Add
PodDisruptionBudget
to helm chart