Roll cephrgw-operator to v0.3.1 (CRD staleness warning) #290
Reference in New Issue
Block a user
Delete Branch "benvin/cephrgw-operator-v0.3.1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
cephrgw-operator v0.3.1 logs a startup WARNING when its installed CRDs are missing or older than the operator (operator repo #6, merged) — added precisely because the CRD tag drifted behind the image before. The new startup check reads the
CustomResourceDefinitionobjects, so it needs a small RBAC grant.Changes
git.unkin.net/unkin/cephrgw-operator→v0.3.1install.yamltag →v0.3.1(keep CRDs in step with the image — the invariant the v0.3.1 warning enforces)apiextensions.k8s.io/customresourcedefinitions: [get, list]to the operator ClusterRole so the startup check is not RBAC-deniedValidated with
kustomize buildon the au-syd1 overlay; the v0.3.1 CRD URL resolves. Supersedes nothing outstanding (the earlier CRD-tag PR #286 to v0.3.0 already merged).https://claude.ai/code/session_016CEncETbf8cvy1PhsHfFHM