← Problem Library
K8s L4 K8S 264 · 18 min

A source-range rule trusts node addresses while externalTrafficPolicy Local leaves one zone with no eligible ingress path during a failover rehearsal

The load balancer policy is correct and locality changes which nodes can actually receive traffic. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.

K8sFoundation OpsLevel 4Free18 min
Scenario

The load balancer policy is correct and locality changes which nodes can actually receive traffic. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.

What to check first
  • Identify the primary failure signal in the Source Policy Correct, Locality Removed the Ingress Path 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.