Production renewals fail only after enabling a stricter runtime class on solver pods while staging continues to pass.
A cert-manager DNS01 renewal works in staging and fails in production
Credentials exist, yet the hardened runtime path cannot read the projected token at the path the solver image expects.
Scenario
What to check first
- Identify the primary failure signal in the The Solver Got the Right Token and Its Runtime Class Refused the Path It Lived On scenario.
- Separate visible symptoms from the underlying technical dependency.
- Describe the safest recovery path and the follow-up prevention work.
Checking checklist
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Inspect runtime-class file access and token projection paths before rotating DNS creds or changing challenge type.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field