Setting up RabbitMQ with Mappia

By default, Mappia doesn't deploy RabbitMQ along with the Helm Chart. This aligns with historical Magento behavior and allows deployment into low-resource environments such as development and pull request previews.

In production environments, RabbitMQ is typically required and can be enabled by following these steps:

Create a secret

This secret stores the RabbitMQ Erlang cookie and the password for the RabbitMQ user user of the cluster. For more information and configuration, see the Bitnami Chart documentation.

kubectl create secret generic my-secret --from-literal=rabbitmq-password=my-password --from-literal=rabbitmq-erlang-cookie=my-password

INFO

The rabbitmq-password and rabbitmq-erlang-cookie are the default key names used by the RabbitMQ chart. You can change them via the rabbitmq.auth.existingSecretPasswordKey and rabbitmq.auth.existingSecretErlangKey.

Configure your values

Now, we can configure your values.yml and proceed with upgrade or install.

rabbitmq:
    enabled: true
    auth:
        existingErlangSecret: my-secret
        existingPasswordSecret: my-secret

Upgrade your chart

helm upgrade my-mappia oci://mappia.azurecr.io/helm/mappia -f values.yml