Charts: [stable/rabbitmq-ha] Deprecated health check spam

[somelinuxguy]

Is your feature request related to a problem? Please describe.

As soon as the helm chart is deployed, the containers begin spamming this message:

2020-07-06 17:58:56.797 [warning] <0.13613.0> rabbitmqctl node_health_check and its HTTP API counterpart are DEPRECATED. See https://www.rabbitmq.com/monitoring.html#health-checks for replacement options.

2020-07-06 17:59:01.808 [warning] <0.13626.0> rabbitmqctl node_health_check and its HTTP API counterpart are DEPRECATED. See https://www.rabbitmq.com/monitoring.html#health-checks for replacement options.

Describe the solution you'd like
Reading the link in the message, there appears to be other ways to perform health-checks. Can this chart be updated to perform one of them, thus eliminating this message? There appears to be no config for me to specify a health check.

Describe alternatives you've considered
Turning off logging. Not super helpful because it avoids the spam but then I don't know if there is a legit issue.

Additional context
This is just a vanilla deploy of the helm chart on to a pretty vanilla cluster at amazon I use for a lab to experiment and research. I just noticed this and wanted to bring it to your attention.

[xlanor]

+. This is also spamming on my end every 5 seconds.

https://github.com/bitnami/bitnami-docker-rabbitmq/issues/122 may be a good reference

[sguidos]

+1 - Do not want to disable logging, but a warning every 5 seconds is excessive, thanks.

[Cna59]

You can changes the check livenessProve && readinessProbe if you want to remove this "spam" warning message in the statefulsets.

kubectl edit statefulsets RELEASE-NAME-rabbitmq-ha

          livenessProbe:
            exec:
              command: ["rabbitmq-diagnostics", "status"]
            failureThreshold: 6
            initialDelaySeconds: 120
            periodSeconds: 10
            timeoutSeconds: 5
          readinessProbe:
            exec:
              command: ["rabbitmq-diagnostics", "status"]

You can also use this one if you want:

["rabbitmq-diagnostics", "check_port_connectivity"]

If you want to update the chart you can edit this file:

vim charts/stable/rabbitmq-ha/values.yaml


livenessProbe:
  initialDelaySeconds: 120
  periodSeconds: 10
  timeoutSeconds: 5
  failureThreshold: 6
  exec:
    command: ["rabbitmq-diagnostics", "status"]

readinessProbe:
  initialDelaySeconds: 20
  periodSeconds: 5
  timeoutSeconds: 3
  failureThreshold: 6
  exec:
    command: ["rabbitmq-diagnostics", "status"]

[ArgTang]

We have changed it to this:

 livenessProbe:
    exec:
      command: ["rabbitmq-diagnostics", "check_running"]
  readinessProbe:
    exec:
      command: ["rabbitmq-diagnostics", "check_local_alarms"]

[steven-sheehy]

This chart has been deprecated and is no longer maintained. It is recommended to use the Bitnami maintained RabbitMQ chart which has a similar feature set, including high availability. See #23746 and #21103. Can you please close. Thanks!