-
Notifications
You must be signed in to change notification settings - Fork 9.5k
[bitnami/external-dns] Major release: drop support for multiple replicas and DaemonSet #26759
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
…cas and DaemonSet Signed-off-by: Miguel Ruiz <miruiz@vmware.com>
Signed-off-by: Miguel Ruiz <miruiz@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Hi, not sure why |
Hi @migruiz4 and @jotamartos, Thanks for your good work :) |
I opened a PR #27467 which disables the pdb. |
please rollback the revisionHistoryLimit change 🙏 it is required and unrelated to these changes |
Created #27913 for the |
Description of the change
External DNS does not officially support deploying multiple replicas or DaemonSet architecture, and doing so may cause issues.
References:
Applicable issues
Additional information
Removed values:
replicaCount
useDaemonset
revisionHistoryLimit
(DaemonSet-only)podDisruptionBudget
(Previously deprecated in favor ofpdb.*
)metrics.serviceMonitor.additionalLabels
(Previously deprecated in favor ofmetrics.serviceMonitor.labels
)Additionally, I added the missing standard value
metrics.serviceMonitor.annotations
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