← Problem Library
K8s L4 K8S 1578 · 9 min

A namespaceSelector update lands and one webhook still ignores a namespace because the label cache keeps the old key spelling

The selector is correct, but one API server cache still stores namespace labels under the previous key spelling.

K8sPlatform ReliabilityLevel 4Pro9 min
Scenario

One webhook ignores a namespace after a selector label rename.

What to check first
  • Identify the primary failure signal in the The New Name Was Written on the Door and One Clerk Still Checked the Attendance Sheet Filed Under the Misspelling Used in the First Draft 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

Inspect label cache invalidation before widening selectors.

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.