← Problem Library
K8s L4 K8S 1434 · 12 min

A cert-manager DNS01 renewal passes staging and fails production

The token exists, yet the challenge helper can no longer read it once the stricter runtime class is applied in production.

K8sPlatform ReliabilityLevel 4Pro12 min
Scenario

Only production DNS challenges begin failing after a runtime hardening rollout.

What to check first
  • Identify the primary failure signal in the The Token Was Projected Correctly and the New Runtime Class Treated Its Path Like Forbidden Ground 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 file access expectations under the new runtime class before rotating credentials or changing solver type.

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.