Bump cephrgw-operator CRDs to v0.3.0 #286

Merged
benvin merged 1 commits from benvin/cephrgw-crd-v0.3.0 into main 2026-07-25 22:34:59 +10:00
Owner

Why

The cephrgw-system kustomization pinned the CRD source to raw/tag/v0.1.0/config/crd/install.yaml, so the in-cluster CRDs never gained the fields added since v0.1.0 — v0.2.0's fine-grained BucketAccess policy fields (paths/actions/conditions/rawStatements) and v0.3.0's adoption fields (retainOnDelete, managePolicy, status.adopted). The running operator is v0.3.0, so applying those specs fails with strict decoding error: unknown field. The image bumps (#273, #279) should have moved this tag too.

Changes

  • point the CRD install.yaml at raw/tag/v0.3.0

The tag must track the operator image tag on future bumps. Verified the v0.3.0 URL serves the new schema and kustomize build renders all 3 CRDs.

https://claude.ai/code/session_016CEncETbf8cvy1PhsHfFHM

## Why The `cephrgw-system` kustomization pinned the CRD source to **`raw/tag/v0.1.0/config/crd/install.yaml`**, so the in-cluster CRDs never gained the fields added since v0.1.0 — v0.2.0's fine-grained BucketAccess policy fields (`paths`/`actions`/`conditions`/`rawStatements`) and v0.3.0's adoption fields (`retainOnDelete`, `managePolicy`, `status.adopted`). The running operator is v0.3.0, so applying those specs fails with `strict decoding error: unknown field`. The image bumps (#273, #279) should have moved this tag too. ## Changes - point the CRD `install.yaml` at `raw/tag/v0.3.0` The tag must track the operator image tag on future bumps. Verified the v0.3.0 URL serves the new schema and `kustomize build` renders all 3 CRDs. https://claude.ai/code/session_016CEncETbf8cvy1PhsHfFHM
unkinben added 1 commit 2026-07-25 22:33:42 +10:00
Bump cephrgw-operator CRDs to v0.3.0
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/kubeconform Pipeline was successful
e2da8fe09c
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
benvin merged commit e4afdf59ba into main 2026-07-25 22:34:59 +10:00
benvin deleted branch benvin/cephrgw-crd-v0.3.0 2026-07-25 22:34:59 +10:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#286