From 07ed39939e18292cf9fcfc0c6b93348fe5e153df Mon Sep 17 00:00:00 2001 From: Niall Thomson Date: Fri, 20 Dec 2024 14:07:37 -0700 Subject: [PATCH] update: Added note related to CoreDNS autoscaling --- .../workloads/cluster-proportional-autoscaler/install.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/docs/autoscaling/workloads/cluster-proportional-autoscaler/install.md b/website/docs/autoscaling/workloads/cluster-proportional-autoscaler/install.md index f0c3799b7..3706ab3e5 100644 --- a/website/docs/autoscaling/workloads/cluster-proportional-autoscaler/install.md +++ b/website/docs/autoscaling/workloads/cluster-proportional-autoscaler/install.md @@ -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"}