Municipal Kubernetes services on Amazon EKS must add pods when CPU or custom metrics rise. Which scaling approach fits container orchestration performance needs?
Select an answer to reveal the explanation.
Short Explanation
K8s already knows how to grow pods when metrics climb—lean on Horizontal Pod Autoscaler–style scaling for city services on EKS. Nightly SSH, one lonely Docker host, or freezing at one replica throws away orchestrated elasticity.
Full Explanation
On Amazon EKS, Horizontal Pod Autoscaler (HPA) adjusts pod replicas based on CPU, memory, or custom metrics, which is the standard orchestration-level scale pattern for containerized municipal services. Manual SSH workflows, non-orchestrated single hosts, and static replica counts do not provide responsive high-performing scale.