Skip to content

feat(rabbitmq): render k8s-operator CRDs for Argo CD - #1

Open
adrien-barret wants to merge 1 commit into
argocdfrom
feat/argocd-rabbitmq
Open

adrien-barret wants to merge 1 commit into
argocdfrom
feat/argocd-rabbitmq

Conversation

@adrien-barret

Copy link
Copy Markdown

Adds argocd.enabled / argocd.org to rabbitmq 1.2.0 so the chart can be deployed by Argo CD through the Control Plane k8s operator, following the postgres/pgvector approach. Default (false) rendering is unchanged.

  • Each resource template is wrapped in if not argocd.enabled and has an argocd-*.yaml sibling emitting cpln.io/v1 CRDs (identity, policy, volumeset, workload) with metadata.namespace = release namespace and org.
  • The rabbitmq.conf secret becomes a native v1 Secret (Opaque, base64 data, cpln.io/org annotation, cpln-operator label).
  • The volumeset carries cpln.io/resource-policy: keep so Argo prune does not delete queue data.
  • No randomness in the base chart; credentials still come from the user-created credentialsSecretName prerequisite secret.

Verification: helm lint passes with argocd.enabled true and false; default render is identical (diff -w -B) to the argocd branch chart; Argo render parses as YAML with apiVersion and namespace on every resource, 5 resources (4 without volumeset), same count as default mode; missing argocd.org fails.

Not converted: nothing (all five templates converted). Risks: the keep annotation means the volumeset must be removed manually; the credentials secret must exist in Control Plane beforehand (unchanged).

Not validated against a live cluster.

🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant