e2da8fe09cbb951387a458ccee6ba578bb9a8c73
The cephrgw-system kustomization pinned the CRD source to tag v0.1.0, so the in-cluster CRDs never gained the fields added since: v0.2.0's fine-grained BucketAccess policy fields and v0.3.0's adoption fields (retainOnDelete, managePolicy, status.adopted). The running operator is v0.3.0, so applying those specs fails strict decoding. Move the CRD tag in step with the image. - point the CRD install.yaml at raw/tag/v0.3.0 Claude-Session: https://claude.ai/code/session_016CEncETbf8cvy1PhsHfFHM
Description
GitOps for ArgoCD
Languages
Shell
88.8%
Makefile
11.2%