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

update: Added note related to CoreDNS autoscaling #1197

Merged
merged 1 commit into from
Dec 20, 2024
Merged

update: Added note related to CoreDNS autoscaling #1197

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
6 changes: 6 additions & 0 deletions website/docs/autoscaling/workloads/cluster-proportional-autoscaler/install.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,12 @@ sidebar_position: 2

CoreDNS is the default DNS service for Kubernetes that runs in Pods with the label `k8s-app=kube-dns`. In this lab exercise we'll scale CoreDNS based on the number of schedulable nodes and cores of our cluster. Cluster Proportional Autoscaler will resize the number of CoreDNS replicas.

:::info

Amazon EKS offers the ability to [automatically scale CoreDNS via the EKS addon](https://docs.aws.amazon.com/eks/latest/userguide/coredns-autoscaling.html), which is the recommended path for production use. The material covered in this lab is for educational purposes.

:::

First lets install CPA using its Helm chart. We'll use the following `values.yaml` file to configure CPA:

::yaml{file="manifests/modules/autoscaling/workloads/cpa/values.yaml" paths="options.target,config.linear.nodesPerReplica,config.linear.min,config.linear.max"}
Expand Down
Loading