edge.24-06-02
Replaces EKS CoreDNS with a custom module, adds monitoring stack with Prometheus and Grafana, introduces Argo Workflow engine, and makes significant improvements to cluster resource utilization and stability.
Migrate EKS CoreDNS to kube_core_dns
The EKS CoreDNS addon has been replaced with the kube_core_dns module.
Add the
dns_service_ipinput toaws_eksdeployments by following this guide. Double check that thedns_service_ipis the same IP as defined bykube-system/kube-dns.Additionally, set
core_dns_addon_enabledtotrue.Apply the updated
aws_eksmodule.Add the
cluster_dns_service_ipinput to yourkube_karpenter_node_poolsmodule, and re-apply the module. Ensure that all of your nodes have been replaced with the new configuration.Deploy
kube_core_dnsby following this guide. Note that this deployment will fail as the original addon service is still running and the IP is already taken.Delete
kube-system/kube-dnsand re-applykube_core_dns. Note that while the service is deleted, DNS will be temporarily unavailable in your cluster.Once you’ve validated that DNS is working in the cluster, remove the
core_dns_addon_enabledinput from theaws_eksmodule 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.