0

I deployed rabbitmq in kubernetes using helm and argocd. Whenever there is any sync it is restarting. Is there any way to curb this behavior and I can manage it with argo without restarts.

Karikaaalan
  • 1

1 Answers1

0

This issue happens because the Bitnami RabbitMQ Helm chart generates a new erlangCookie (a Kubernetes Secret) on every Helm template render if auth.erlangCookie is not explicitly set. This causes a change in the pod template annotations (checksum/secret), which in turn triggers a rolling restart of the StatefulSet during every ArgoCD sync — even if nothing functionally changed.

Solution:

To prevent this, explicitly set a fixed erlangCookie in your values.yaml file:

auth:
  securePassword: true
  erlangCookie: "MySuperSecretFixedErlangCookieRabbitMQ"

This makes the rendered manifests deterministic and stops ArgoCD from triggering unnecessary restarts on sync.

Михаил Волошин
  • 1