edge.24-06-02

Migrate EKS CoreDNS to kube_core_dns

The EKS CoreDNS addon has been replaced with the kube_core_dns module.

1. Add the dns_service_ip input to aws_eks deployments by following this guide. Double check that the dns_service_ip is the same IP as defined by kube-system/kube-dns.

2. Additionally, set core_dns_addon_enabled to true.

3. Apply the updated aws_eks module.

4. Add the cluster_dns_service_ip input to your kube_karpenter_node_pools module, and re-apply the module. Ensure that all of your nodes have been replaced with the new configuration.

5. Deploy kube_core_dns by following this guide. Note that this deployment will fail as the original addon service is still running and the IP is already taken.

6. Delete kube-system/kube-dns and re-apply kube_core_dns. Note that while the service is deleted, DNS will be temporarily unavailable in your cluster.

7. Once you’ve validated that DNS is working in the cluster, remove the core_dns_addon_enabled input from the aws_eks module and re-apply.

Fix Label Selectors

Label selectors in kube_pod have been stabilized, but require a one-time manual deletion of already-deployed Deployments before re-applying.

Delete the bastion/bastion deployment (and any other deployments created by kube_deployment) before running terragrunt apply.