-
Notifications
You must be signed in to change notification settings - Fork 4
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
Migrate away from Bitnami external-dns to official chart #1744
Comments
nimalank7
added a commit
that referenced
this issue
Apr 10, 2024
Description: - Official Kubernetes external-dns chart is located [here](https://github.com/kubernetes-sigs/external-dns/tree/master/charts/external-dns) - Previously in production we were running 3 but the bitnami chart doesn’t have any leader selection so all external-dnspods were running thinking they were the only one. Kubernetes external-dns doesn’t support multiple replicas so removing this entirely. See the discussion [here](kubernetes-sigs/external-dns#2430) - PR closes #1744
nimalank7
added a commit
that referenced
this issue
Apr 10, 2024
Description: - Official Kubernetes external-dns chart is located [here](https://github.com/kubernetes-sigs/external-dns/tree/master/charts/external-dns) - Previously in production we were running 3 but the bitnami chart doesn’t have any leader selection so all external-dnspods were running thinking they were the only one. Kubernetes external-dns doesn’t support multiple replicas so removing this entirely. See the discussion [here](kubernetes-sigs/external-dns#2430) - PR closes #1744
nimalank7
added a commit
that referenced
this issue
Apr 11, 2024
Description: - Official Kubernetes external-dns chart is located [here](https://github.com/kubernetes-sigs/external-dns/tree/master/charts/external-dns) - Previously in production we were running 3 but the bitnami chart doesn’t have any leader selection so all external-dnspods were running thinking they were the only one. Kubernetes external-dns doesn’t support multiple replicas so removing this entirely. See the discussion [here](kubernetes-sigs/external-dns#2430) - PR closes #1744
nimalank7
added a commit
that referenced
this issue
Apr 11, 2024
Description: - Official Kubernetes external-dns chart is located [here](https://github.com/kubernetes-sigs/external-dns/tree/master/charts/external-dns) - Previously in production we were running 3 but the bitnami chart doesn’t have any leader selection so all external-dnspods were running thinking they were the only one. Kubernetes external-dns doesn’t support multiple replicas so removing this entirely. See the discussion [here](kubernetes-sigs/external-dns#2430) - PR closes #1744
nimalank7
added a commit
that referenced
this issue
Apr 11, 2024
Description: - Official Kubernetes external-dns chart is located [here](https://github.com/kubernetes-sigs/external-dns/tree/master/charts/external-dns) - Previously in production we were running 3 but the bitnami chart doesn’t have any leader selection so all external-dnspods were running thinking they were the only one. Kubernetes external-dns doesn’t support multiple replicas so removing this entirely. See the discussion [here](kubernetes-sigs/external-dns#2430) - PR closes #1744
nimalank7
added a commit
that referenced
this issue
Apr 11, 2024
Description: - Use the correct syntax for external-dns deployment strategy - Related to #1744
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're using the Bitnami external-dns chart at the moment, but their charts repo is huge and contains hundreds of charts, which makes it difficult to see what has changed when updates are released. There is an official external-dns chart, which we could use instead.
https://github.com/kubernetes-sigs/external-dns/tree/master/charts/external-dns
The text was updated successfully, but these errors were encountered: