-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
[bitnami/external-dns] PDB fixes #26292
Conversation
Signed-off-by: Fran Mulero <fmulero@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Fran Mulero <fmulero@vmware.com>
… into bugfix/external-dns-pdb-2
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
…-pdb-2 Signed-off-by: Fran Mulero <fmulero@vmware.com>
… into bugfix/external-dns-pdb-2
Signed-off-by: Fran Mulero <fmulero@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
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.
We should keep 1 replica by default and set pdb.maxUnavailable
instead.
pdb:
minAvailable: ""
maxUnavailable: 1
With those defaults, if any user tries to install the chart setting only `pdb.minAvailable=1' this error will be faced: $ helm install test bitnami/external-dns --set pdb.minAvailable=1
Error: INSTALLATION FAILED: PodDisruptionBudget.policy "test-external-dns" is invalid: spec: Invalid value: policy.PodDisruptionBudgetSpec{MinAvailable:(*intstr.IntOrString)(0xc00d46e580), Selector:(*v1.LabelSelector)(0xc00d46e5a0), MaxUnavailable:(*intstr.IntOrString)(0xc00d46e560), UnhealthyPodEvictionPolicy:(*policy.UnhealthyPodEvictionPolicyType)(nil)}: minAvailable and maxUnavailable cannot be both set Users should unset With the current approach that is not needed. Users settings take precedence but if |
Signed-off-by: Fran Mulero <fmulero@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Juan Ariza Toledano <jariza@vmware.com> Signed-off-by: Fran Mulero <francisco-jose.mulero@broadcom.com>
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.
LGTM
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
* [bitnami/external-dns] PDB fixes Signed-off-by: Fran Mulero <fmulero@vmware.com> * Update CHANGELOG.md Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * Set pdb.maxUnavailable instead of pdb.minAvailable by default Signed-off-by: Fran Mulero <fmulero@vmware.com> * Update CHANGELOG.md Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * Fix CHANGELOG.md Signed-off-by: Fran Mulero <fmulero@vmware.com> * Update CHANGELOG.md Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * Add documentation for pdb.maxUnavailable value Signed-off-by: Fran Mulero <fmulero@vmware.com> * Update CHANGELOG.md Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> * Update bitnami/external-dns/values.yaml Co-authored-by: Juan Ariza Toledano <jariza@vmware.com> Signed-off-by: Fran Mulero <francisco-jose.mulero@broadcom.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> --------- Signed-off-by: Fran Mulero <fmulero@vmware.com> Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com> Signed-off-by: Fran Mulero <francisco-jose.mulero@broadcom.com> Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com> Co-authored-by: Juan Ariza Toledano <jariza@vmware.com> Signed-off-by: Fran Mulero <fmulero@vmware.com>
Description of the change
Remove default value for
pdb.minAvailable
and setmaxUnavailable
to 1 in PodDisruptionBudgets if none is set.Benefits
Maintenance to infrastructure is allowed with chart defaults.
Possible drawbacks
Some users could expect old value in
minAvailable
. In that case the value should be set explicitly.Applicable issues
Additional information
Follow up #25933
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm