Deploy the RabbitMQ Operator and a RabbitMQ Cluster

Deploy the RabbitMQ operator.

kubectl apply -k /etc/genestack/kustomize/rabbitmq-operator

Note

The operator may take a minute to get ready, before deploying the RabbitMQ cluster, wait until the operator pod is online.

Deploy the RabbitMQ topology operator.

kubectl apply -k /etc/genestack/kustomize/rabbitmq-topology-operator

Deploy the RabbitMQ cluster.

kubectl apply -k /etc/genestack/kustomize/rabbitmq-cluster/overlay

Note

RabbitMQ has a base configuration which is HA and production ready. If you're deploying on a small cluster the aio configuration may better suit the needs of the environment.

Validate the status with the following

kubectl --namespace openstack get rabbitmqclusters.rabbitmq.com -w

RabbitMQ Operator Monitoring

RabbitMQ Operator provides ServiceMonitor and PodMonitor CRDs to expose scrape endpoints for rabbitmq cluster and operator.

Warning

Make sure Prometheus Operator is deployed prior to running these commands. It will error out if the rquired CRDs are not already installed.

Check if the required CRDs are installed

kubectl get customresourcedefinitions.apiextensions.k8s.io servicemonitors.monitoring.coreos.com

if the CRDs are present you can run the following

kubectl apply --filename https://raw.githubusercontent.com/rabbitmq/cluster-operator/main/observability/prometheus/monitors/rabbitmq-servicemonitor.yml

kubectl apply --filename https://raw.githubusercontent.com/rabbitmq/cluster-operator/main/observability/prometheus/monitors/rabbitmq-cluster-operator-podmonitor.yml

then,

for file in $(curl -s https://api.github.com/repos/rabbitmq/cluster-operator/contents/observability/prometheus/rules/rabbitmq | jq -r '.[].download_url'); do   kubectl apply -n prometheus -f $file; done

for file in $(curl -s https://api.github.com/repos/rabbitmq/cluster-operator/contents/observability/prometheus/rules/rabbitmq-per-object | jq -r '.[].download_url'); do   kubectl apply -n prometheus -f $file; done

In order for these to work we need to also make sure that they match the ruleSelector from Prometheus deploy. For genestack deploys run

kubectl get prometheusrule -n prometheus -o name | xargs -I {} kubectl label -n prometheus {} release=kube-prometheus-stack --overwrite

This will get all the rules in prometheus namespace and apply release=kube-prometheus-stack label. At this point the alerts will be configured in prometheus.