When a Claw deployment fails due to init container crashes, the operator reports only "Waiting for deployments to become ready" — forcing users to dig through pod logs. The most common production failure we observed was a version mismatch: spec.version set to an older tag against a PVC configured for a newer one, causing plugin init containers to crash-loop. The operator had no way to surface the root cause.
Additionally, version downgrades (setting spec.version to a value older than what was previously deployed) can cause PVC data incompatibility. Users need a warning before they discover the problem at runtime.
See https://github.com/redhat-et/claw-operator/tree/main/openspec/changes/add-status-warnings
When a Claw deployment fails due to init container crashes, the operator reports only "Waiting for deployments to become ready" — forcing users to dig through pod logs. The most common production failure we observed was a version mismatch:
spec.versionset to an older tag against a PVC configured for a newer one, causing plugin init containers to crash-loop. The operator had no way to surface the root cause.Additionally, version downgrades (setting
spec.versionto a value older than what was previously deployed) can cause PVC data incompatibility. Users need a warning before they discover the problem at runtime.See https://github.com/redhat-et/claw-operator/tree/main/openspec/changes/add-status-warnings