← Problem Library
K8s L5 K8S 1428 · 14 min

A Velero restore brings back CRDs and one controller never stabilizes

Objects restore in order, yet one controller caches the early webhook failure and never retries conversion until it restarts.

K8sPlatform ReliabilityLevel 5Pro14 min
Scenario

A restore seems complete and one custom-controller workflow remains broken until the controller pod is bounced.

What to check first
  • Identify the primary failure signal in the The Webhook Service Came Back First and the Controller Remembered Its First Failure Like a Permanent Fact scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Inspect controller retry and cache behavior around early conversion failures before editing the restored CRs.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.