Scenario
HTTP01 validation fails only on one ingress path after solver updates.
A cert-manager HTTP01 solver is patched and one order still fails because the old ingressClassName annotation wins over the spec field
The solver config is current, but one ingress controller still prioritizes the legacy annotation during challenge routing.
What to check first
- Identify the primary failure signal in the The New Address Was Written on the Envelope and One Mail Sorter Still Followed the Sticker That Had Been Used Before the Form Was Redesigned 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 annotation precedence before changing DNS.
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