Vertical Pod Autoscalers (VPA) adjust which pod characteristics?

Vertical Pod Autoscalers (VPA) adjust which pod characteristics?

• A. The number of replicas for a deployment
• B. The scheduling constraints of pods
• C. The resource requests and limits of a pod
• D. The namespace quotas

Answer: (C)

Vertical Pod Autoscaler focuses on giving a pod the right amount of resources by adjusting its container resource requests and limits (CPU and memory). This helps the scheduler reserve appropriate resources and prevents under- or over-provisioning of a pod. It does not change how many pods exist—that’s handled by horizontal scaling. It also isn’t about scheduling constraints like affinity rules, tolerations, or quotas at the namespace level. Those are separate concerns: constraints determine where a pod can run, and quotas limit total resources in a namespace. When VPA updates a PodSpec, you typically apply new resource requests/limits to trigger a rollout so the running pods use the updated resources. In short, VPA adjusts resource requests and limits, not the number of replicas or scheduling constraints.

Vertical Pod Autoscaler focuses on giving a pod the right amount of resources by adjusting its container resource requests and limits (CPU and memory). This helps the scheduler reserve appropriate resources and prevents under- or over-provisioning of a pod.

It does not change how many pods exist—that’s handled by horizontal scaling. It also isn’t about scheduling constraints like affinity rules, tolerations, or quotas at the namespace level. Those are separate concerns: constraints determine where a pod can run, and quotas limit total resources in a namespace.

When VPA updates a PodSpec, you typically apply new resource requests/limits to trigger a rollout so the running pods use the updated resources. In short, VPA adjusts resource requests and limits, not the number of replicas or scheduling constraints.