← Problem Library
K8s L4 K8S 1469 · 10 min

An Istio WebSocket path keeps the TCP session and still loses auth because the upgrade branch skips a header rewrite

The socket stays open, but the auth header mutation only exists on the non-upgrade route.

K8sPlatform ReliabilityLevel 4Pro10 min
Scenario

Normal API calls pass and WebSocket upgrades lose authentication after a routing cleanup.

What to check first
  • Identify the primary failure signal in the The Socket Stayed Open and the Header Rewrite Waited in a Route the Upgrade Never Visited 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 upgrade and non-upgrade route branches before rotating tokens or changing origin config.

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.