← Problem Library
K8s L4 K8S 1393 · 12 min

A Karpenter or autoscaler scale-from-zero path stalls

The pod becomes schedulable after mutation, yet the provisioning decision was already made against the pre-mutated spec.

K8sPlatform ReliabilityLevel 4Pro12 min
Scenario

A scale-from-zero workflow works for some workloads and later one class of pods remains pending despite enough node templates existing.

What to check first
  • Identify the primary failure signal in the The Pod Learned the Right Toleration After the Provisioner Had Already Given Up 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 pre- and post-admission pod specs before editing node pools or taints.

Questions worth viewing together
What should you verify first when A Karpenter or autoscaler scale-from-zero path stalls appears?

Community-field Kubernetes problem inspired by autoscaler and webhook discussions where provisioning never saw the post-mutation toleration set. Provisioning decisions can be made on an earlier pod shape than the one you inspect later.

What usually causes A Karpenter or autoscaler scale-from-zero path stalls in production?

Teams often blame autoscaler capacity when admission mutation is what changed the scheduling contract after the decision point.

What should you document after resolving A Karpenter or autoscaler scale-from-zero path stalls?

Any admission mutation that affects scheduling should be validated against scale-from-zero provisioning logic.