A DevOps team is deploying microservices for an application on an Amazon Elastic Kubernetes Service (Amazon EKS) cluster. The cluster uses managed node groups. The DevOps team wants to enable auto…

Question

Options

• AEdit the Auto Scaling group that is associated with the worker nodes of the EKS cluster.
• BDeploy the Kubernetes Horizontal Pod Autoscaler (HPA) and the Kubernetes Vertical Pod
• CRun the AWS Systems Manager AWS-UpdateEKSManagedNodeGroup Automation document.
• DDeploy the Kubernetes Horizontal Pod Autoscaler (HPA) and the Kubernetes Cluster Autoscaler

• A
  6% (3)
• B
  15% (8)
• C
  4% (2)
• D
  76% (41)

Explanation

The HPA is a Kubernetes-native feature designed specifically to scale Pods based on resource utilization, such as CPU or memory. In this case, you want to scale based on CPU utilization, which HPA handles efficiently by adjusting the number of Pods in response to the CPU load. The Cluster Autoscaler works alongside the HPA to automatically add or remove nodes in the EKS cluster depending on the overall capacity required by the running Pods. When the HPA scales up the number of Pods and more nodes are required, the Cluster Autoscaler ensures the infrastructure can handle the load. The auto-discovery setting makes this scaling process even more efficient, automatically detecting the resources needed without manual intervention. By using HPA and Cluster Autoscaler together, you ensure efficient and dynamic scaling of both Pods and nodes based on actual CPU usage, resulting in an operationally efficient solution that adjusts to the application's needs in real time.

No community discussion yet for this question.