← Problem Library
K8s L4 K8S 345 · 18 min

A topology spread rule looks balanced while one tainted node pool is the only place the emergency fallback pods are actually allowed to run during a staged decommission

Distribution appears fair until a failure forces the scheduler into the only domain with compatible taints. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.

K8sFoundation OpsLevel 4Free18 min
Scenario

Distribution appears fair until a failure forces the scheduler into the only domain with compatible taints. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.

What to check first
  • Identify the primary failure signal in the Balanced Spread Rules, Unbalanced Emergency Reality 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

Choose the smallest safe recovery action first, then record the prevention work that reduces repeat incidents.

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.