rabbitmq-cluster-operator-advanced

The RabbitMQ Cluster Kubernetes Operator automates provisioning, management, and operations of RabbitMQ clusters running on Kubernetes. The RabbitMQ Cluster Operator Helm chart automates deployment and configuration of the RabbitMQ Cluster Operator in Kubernetes clusters using Minimus images.

Prerequisites

A subscription to the Minimus images included in the chart
A running Kubernetes cluster (v1.19 or higher is recommended)
kubectl installed and configured
Helm v3.8 or higher for OCI support (Installation instructions)
Cluster Admin privileges

Note: The RabbitMQ Cluster Operator installs Custom Resource Definitions (CRDs) for RabbitmqCluster resources. These CRDs are installed automatically as part of the Helm chart deployment and require Cluster Admin privileges.

Try It Out

In this example we will deploy the RabbitMQ Cluster Operator on a Kubernetes cluster using the Minimus RabbitMQ Cluster Operator Helm chart. The operator will enable you to declaratively create and manage RabbitMQ clusters using Kubernetes custom resources.

Step 1: Start Cluster

If you have a cluster to work with, skip this step. Otherwise, start a Minikube cluster. Deployment instructions

Step 2: Create Namespace

Create a namespace:

kubectl create ns rabbitmq-cluster-operator

Step 3: Deploy the Helm Chart

Deploy the Minimus Helm chart:

helm install my-rabbitmq-cluster-operator oci://helm.mini.dev/rabbitmq-cluster-operator-advanced \
  --version 4.4.34 \
  -n rabbitmq-cluster-operator \
  --wait

If you want to override the chart's defaults, go to the Values tab, save a copy locally with your changes. Deploy the chart with your overrides using -f values.yaml:

helm install my-rabbitmq-cluster-operator oci://helm.mini.dev/rabbitmq-cluster-operator-advanced \
  --version 4.4.34 \
  -f values.yaml \
  -n rabbitmq-cluster-operator \
  --wait

Step 4: Verify RabbitMQ Cluster Operator is Running

Confirm the chart deployed successfully and the operators started:

kubectl get pods -n rabbitmq-cluster-operator

You should see output similar to:

NAME                                                              READY   STATUS    RESTARTS   AGE
my-rabbitmq-cluster-operator-xxxxxxxxx-xxxxx                      1/1     Running   0          2m
my-rabbitmq-cluster-operator-msgTopologyOperator-xxxxxxxxx-xxxxx  1/1     Running   0          2m

Step 5: Test RabbitMQ Cluster Provisioning

Create a minimal RabbitmqCluster custom resource to verify the operator is working:

cat <<EOF | kubectl apply -f -
apiVersion: rabbitmq.com/v1beta1
kind: RabbitmqCluster
metadata:
  name: test-rabbit
  namespace: rabbitmq-cluster-operator
spec:
  replicas: 1
EOF

Wait for the RabbitmqCluster to become ready:

kubectl wait --for=condition=AllReplicasReady rabbitmqcluster/test-rabbit \
  -n rabbitmq-cluster-operator --timeout=180s

You should see:

rabbitmqcluster.rabbitmq.com/test-rabbit condition met

Verify the RabbitMQ pod is running:

kubectl get pods -n rabbitmq-cluster-operator -l app.kubernetes.io/name=test-rabbit

Clean up the test cluster:

kubectl delete rabbitmqcluster/test-rabbit -n rabbitmq-cluster-operator

Step 6: Clean Up

Uninstall the chart and delete the namespace to remove all resources:

helm uninstall my-rabbitmq-cluster-operator -n rabbitmq-cluster-operator
kubectl delete namespace rabbitmq-cluster-operator

Terms & Info

Trademark

This catalog is published by Minimus. All product names, logos, and marks, other than those belonging to Minimus, shown are owned by their respective rights holders and appear here only to identify the open source software each image contains. Minimus claims no ownership of those marks and implies no affiliation with, endorsement by, certification by, or sponsorship by any rights holder.

Disclaimer

Images are provided "as-is" without warranty of any kind. "Hardened" refers to the security configuration applied at the time of build and does not constitute a guarantee of ongoing security or absence of vulnerabilities. The free tier is provided without support, SLA, or guaranteed patching timelines. Security updates may be applied to paid subscriptions before or instead of free tier images. By pulling or using any image you agree to our Terms of Use.

This page is available on desktop