Correct Answer: cluster-autoscaler.kubernetes.io/safe-to-evict: "false"
The Cluster Autoscaler respects the pod annotation cluster-autoscaler.kubernetes.io/safe-to-evict: 'false'. When this annotation is set to false, CA will avoid scaling down or drai...
Correct Answer
cluster-autoscaler.kubernetes.io/safe-to-evict: "false"
Why This Answer Is Correct
The Cluster Autoscaler respects the pod annotation cluster-autoscaler.kubernetes.io/safe-to-evict: 'false'. When this annotation is set to false, CA will avoid scaling down or draining the node running this pod to prevent interrupting the pod's execution.
This question evaluates your knowledge of Kubernetes Autoscaling — a core concept tested in cloud certification exams. Understanding Kubernetes Autoscaling is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
What does a HorizontalPodAutoscaler (HPA) do when CPU utilization exceeds the defined target?
You want to scale the number of replicas in your frontend deployment based on custom metrics retrieved from Prometheus, rather than standard CPU or Memory utilization. Which Kubernetes autoscaling component should you use?
A DevOps team is running a microservice deployment and wants to configure both Horizontal Pod Autoscaler (HPA) to scale out based on CPU usage and Vertical Pod Autoscaler (VPA) to scale resources up/down. What is the recommended practice when using both autoscalers on the same deployment?
During traffic peaks, your Horizontal Pod Autoscaler (HPA) scales out replicas rapidly. However, when traffic dips briefly, the HPA immediately scales down, causing resource thrashing. How can you configure HPA to delay scaling down and stabilize replica count?