[Solved] You applied this HPA YAML but it does not scale pods as expected:apiVersion: autoscaling/v2 kind: HorizontalPodAutoscaler metadata: name: test-hpa spec: scaleTargetRef: apiVersion: apps/v1 kind:... | Kubernetes

Kubernetes - Resource Management

You applied this HPA YAML but it does not scale pods as expected:

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: test-hpa
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: test-app
  minReplicas: 2
  maxReplicas: 5
  metrics:
  - type: Resource
    resource:
      name: memory
      target:
        type: Utilization
        averageUtilization: 70

What is the most likely reason for no scaling?

AThe pods do not expose memory metrics, so HPA has no data

BminReplicas is set too low

CmaxReplicas is less than minReplicas

DThe deployment name is incorrect

Step-by-Step Solution

Solution:

Step 1: Check metric type and data availability
HPA needs metrics from pods. If memory metrics are not exposed or collected, HPA cannot scale.
Step 2: Verify other spec values
minReplicas and maxReplicas are valid (2 and 5). Deployment name looks correct. So likely missing metrics cause no scaling.
Final Answer:
The pods do not expose memory metrics, so HPA has no data -> Option A
Quick Check:
Missing metrics = no scaling [OK]

Quick Trick: HPA needs metrics; no metrics means no scaling [OK]

Common Mistakes:

Assuming minReplicas too low stops scaling
Confusing minReplicas and maxReplicas values
Ignoring metric availability

Master "Resource Management" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Kubernetes Quizzes

You applied this HPA YAML but it does not scale pods as expected:

Step 1: Check metric type and data availability

Step 2: Verify other spec values

Final Answer:

Quick Check:

Want More Practice?