Replace the Bitnami external-dns Helm chart with the official one
Overview
Bitnami will stop updating their external-dns container image on August 28th (see announcement), so it needs to be replaced before then.
While their external-dns Helm chart will continue to be maintained, its future remains uncertain and we wouldn't want to risk having to replace it on short notice again.
The official external-dns Helm chart is decent enough and can safely be migrated to in place, after re-adding some missing resources (PodDisruptionBudget and NetworkPolicy) via an extra chart.
Proposed plan of action
In k8s-workloads/gitlab-helmfiles:
- update chart reference to use https://kubernetes-sigs.github.io/external-dns/v0.18.0/
- update chart values to match the current ones
- add a local
external-dns-extrasHelm chart re-adding thePodDisruptionBudgetandNetworkPolicyresources
- update chart reference to use https://kubernetes-sigs.github.io/external-dns/v0.18.0/
- update chart values to match the current ones
- add a local kustomizations re-adding the
PodDisruptionBudgetandNetworkPolicyresources
TODO: figure out how to prevent Helm from uninstalling the CRD during the switch, and how to keep it updated automatically moving forward
Exit Criteria
-
k8s-workloads/gitlab-helmfilesdeploysexternal-dnsusing its official Helm chart -
k8s-mgmt/componentsdeploysexternal-dnsusing its official Helm chart
Edited by Pierre Guinoiseau