Scenario
Availability degrades quietly because the scheduler still honors availability under pressure, just not in the way the team assumed.
Pod anti-affinity is only preferred, so after a zone loss the replacement replicas pile onto one node and the next failure takes out the whole service
Availability degrades quietly because the scheduler still honors availability under pressure, just not in the way the team assumed.
What to check first
- Identify the primary failure signal in the Preferred Is Not Protective Enough scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- 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
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field