Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update coredns-autoscaling.md #770

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update coredns-autoscaling.md #770

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc_source/coredns-autoscaling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

When you launch an Amazon EKS cluster with at least one node, a Deployment of two replicas of the CoreDNS image are deployed by default, regardless of the number of nodes deployed in your cluster\. The CoreDNS Pods provide name resolution for all Pods in the cluster\. Applications use name resolution to connect to pods and services in the cluster as well as connecting to services outside the cluster\. As the number of requests for name resolution \(queries\) from pods increase, the CoreDNS pods can get overwhelmed and slow down, and reject requests that the pods can’t handle\.

To handle the increased load on the CoreDNS pods, consider an autoscaling system for CoreDNS\. Amazon EKS can manage the autoscaling of the CoreDNS Deployment in the EKS Add\-on version of CoreDNS\. This CoreDNS autoscaler continuously monitors the cluster state, including the number of nodes and CPU cores\. Based on that information, the controller will dynamically adapt the number of replicas of the CoreDNS deployment in an EKS cluster\. This feature works for CoreDNS `v1.9` and EKS release version `1.25` and later\. For more information about which versions are compatible with CoreDNS Autoscaling, see the following section\.
To handle the increased load on the CoreDNS pods, consider an autoscaling system for CoreDNS\. Amazon EKS can manage the autoscaling of the CoreDNS Deployment in the EKS Add\-on version of CoreDNS\. This CoreDNS autoscaler continuously monitors the cluster state for the number of nodes and CPU cores\. Based on that information, the controller will dynamically adapt the number of replicas of the CoreDNS deployment in an EKS cluster\. This feature works for CoreDNS `v1.9` and EKS release version `1.25` and later\. For more information about which versions are compatible with CoreDNS Autoscaling, see the following section\.

We recommend using this feature in conjunction with other [EKS Cluster Autoscaling best practices](https://aws.github.io/aws-eks-best-practices/cluster-autoscaling/) to improve overall application availability and cluster scalability\.

Expand Down Expand Up @@ -218,4 +218,4 @@ Every platform version of later Kubernetes versions are also supported, for exam
aws eks describe-addon --cluster-name my-cluster --addon-name coredns \
```

If you see this line: `"status": "ACTIVE"`, then the rollout has completed and the add\-on is using the new configuration in all of the CoreDNS pods\. As you change the number of nodes and CPU cores of nodes in the cluster, Amazon EKS scales the number of replicas of the CoreDNS deployment\.
If you see this line: `"status": "ACTIVE"`, then the rollout has completed and the add\-on is using the new configuration in all of the CoreDNS pods\. As you change the number of nodes and CPU cores of nodes in the cluster, Amazon EKS scales the number of replicas of the CoreDNS deployment\.