Certificate issuance fails only on the canary ingress path after a mesh rollout.
A cert-manager HTTP01 challenge works on the base gateway and fails on the...
The challenge route exists, but the canary gateway applies an extra rewrite chain the base gateway does not.
Scenario
What to check first
- Identify the primary failure signal in the The Challenge Path Reached the Mesh and the Canary Sent It Down the Wrong Corridor 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 challenge routing between base and canary gateways 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