← Problem Library
K8s L5 K8S 1489 · 10 min

An HPA sees rising load and refuses to scale because Prometheus Adapter still serves an old label set for the renamed deployment

Metrics exist, but the adapter query returns labels that no longer match the current workload selector.

K8sPlatform ReliabilityLevel 5Pro10 min
Scenario

Autoscaling stops only after a deployment rename and metrics adapter refresh that otherwise looks healthy.

What to check first
  • Identify the primary failure signal in the The Traffic Went Up and the Adapter Kept Asking for the Deployment by the Name It Had Before the Rename scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Compare custom metric label selectors before tuning HPA thresholds.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.