Certificate issuance fails only after canary ingress annotations are added for a blue-green rollout.
A cert-manager HTTP01 challenge reaches the ingress and still fails because an NGINX canary annotation rewrites only the challenge path
The solver service exists, but one annotation routes the ACME path to the wrong backend branch.
Scenario
What to check first
- Identify the primary failure signal in the The Challenge Reached the Ingress and the Canary Signpost Sent It Down the Wrong Hallway 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
Compare ACME path routing and canary annotations before changing DNS or solver pods.
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