Scenario
Only one API server reports x509 webhook errors after certificate rotation.
An admission webhook cert rotates and one API server still reports x509 errors because its aggregator cache pins the retired bundle
The webhook secret is current, but one API server continues validating against a cached ca bundle in the aggregator path.
What to check first
- Identify the primary failure signal in the The New Certificate Was Posted at the Front Desk and One Inspector Kept Comparing It With the Copy He Had Folded Into His Notebook Last Week 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 aggregator caches before regenerating webhook certs again.
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