fix: add erlang cookie for rabbitmq

freeleaps/helm-pkg/3rd/rabbitmq/values.alpha.yaml

@@ -25,6 +25,7 @@ auth:
   securePassword: true
   updatePassword: false
   enableLoopbackUser: false
+  erlangCookie: "iGF4ZVjeaXgHW2xELZTxJl8a6aFY7nes"
   tls:
     enabled: false
 logs: "-"
@@ -186,7 +187,7 @@ extraConfiguration: |-
   disk_free_limit.absolute = 50MB
 replicaCount: 1
 updateStrategy:
-  type: Recreate
+  type: RollingUpdate
 podSecurityContext:
   enabled: true
   fsGroupChangePolicy: Always

freeleaps/helm-pkg/3rd/rabbitmq/values.prod.yaml

@@ -162,6 +162,7 @@ auth:
   ## ref: https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq#environment-variables
   ##
   updatePassword: false
+  
   ## @param auth.existingPasswordSecret Existing secret with RabbitMQ credentials (existing secret must contain a value for `rabbitmq-password` key or override with setting auth.existingSecretPasswordKey)
   ## e.g:
   ## existingPasswordSecret: name-of-existing-secret
@@ -177,7 +178,7 @@ auth:
   ## @param auth.erlangCookie Erlang cookie to determine whether different nodes are allowed to communicate with each other
   ## ref: https://github.com/bitnami/containers/tree/main/bitnami/rabbitmq#environment-variables
   ##
-  erlangCookie: ""
+  erlangCookie: "iGF4ZVjeaXgHW2xELZTxJl8a6aFY7nes"
   ## @param auth.existingErlangSecret Existing secret with RabbitMQ Erlang cookie (must contain a value for `rabbitmq-erlang-cookie` key or override with auth.existingSecretErlangKey)
   ## e.g:
   ## existingErlangSecret: name-of-existing-secret