Did you review the description of the health issues reported for the CoreDNS add-on?
You can get the description of the health issues reported for the add-on by following the steps below:
AWS Console >> EKS Clusters >> click the cluster name >> add-ons >> coredns >> Health Issues
The CoreDNS status can be Degraded if there are no worker nodes in the EKS Cluster causing the CoreDNS add-on to encounter InsufficientNumberOfReplicas health issues i.e to be unhealthy because it doesn't have the desired number of replicas.
To resolve this issue, follow the steps here to launch Amazon EKS managed node groups of nodes that register with your Amazon EKS cluster.
EKS Cluster was create Security Group and don't cleanup this SG after destroyasked a month ago
Kubernetes trying to create a production worthy EKS cluster.asked 20 days ago
How to remove a specific node from EKS node group (none managed eksctl)Accepted Answerasked 2 months ago
EKS Node Group with RIAccepted AnswerEXPERTasked 2 years ago
EKS static IPs for managed node group nodesAccepted Answerasked 2 years ago
add node into node groupasked 4 months ago
EKS can't scale Managed Node Group from 0asked 5 months ago
How to create EKS cluster with dedicated host node groupAccepted Answerasked 10 months ago
coredns remains Degraded after EKS cluster creationasked a month ago
Unable to create EKS Clusterasked 5 months ago