Scenario
One cert-manager order remains pending after issuer switch.
A cert-manager issuer switch is correct and one order still waits because the old secretRef alias survives in the approver cache
The issuer spec is updated, but one approver path still resolves the older secretRef alias and leaves the order pending.
What to check first
- Identify the primary failure signal in the The New Stamp Office Opened and One Clerk Still Searched for the Seal Filed Under the Nickname Used on the Temporary Sign 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 cached issuer references before reissuing the request.
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