← Problem Library
K8s L6 K8S 1490 · 11 min

An ingress-nginx admission patch succeeds and websocket upgrades still fail because one canary path bypasses the shared keepalive annotations

Most traffic upgrades correctly, but the canary branch reaches an upstream block that lacks the shared websocket tuning.

K8sPlatform ReliabilityLevel 6Pro11 min
Scenario

WebSocket upgrades fail only for canary users after ingress annotations were centralized.

What to check first
  • Identify the primary failure signal in the The Ingress Looked Patched and the Canary Walked Around the Part That Actually Knows How to Keep a Socket Alive 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 canary path inheritance and upstream keepalive settings before changing the app.

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.