Pods keep crashing when specified communityPlugins options about charts HOT 6 CLOSED

Yeah I agree. We have automated chart upgrades for our external charts. So we upgrade to latest version once every week.

I can see this possibly 'defeating' the purpose. But it fixes for now to maintain uptime. Going to look into the changes soon.

from charts.

Hi everyone! I just created a PR to address this issues so it's possible to install custom plugins without reverting security defaults.

from charts.

Hi,

Just had a similar issue with helm chart version 13.0.0. The below may help?

It looks like some default values have been added to the statefulset and when deployed it was crashing one of my nodes.

This is what has changed:

I added this to my values (which it was previously) and it has fixed it:

containerSecurityContext:
  readOnlyRootFilesystem: false
  runAsGroup: 0

from charts.

Thanks, This fixes the issue.
Reason we are using 13.0.0 release is the security improvements we got, this might defeat the purpose.

from charts.

Hello @pidge-raman, this is indeed an issue introduced in the new major which I could reproduce locally:

$ kubectl logs rabbitmq-0
...
rabbitmq 16:35:09.70 INFO  ==> Validating settings in RABBITMQ_* env vars..
rabbitmq 16:35:09.71 INFO  ==> Initializing RabbitMQ...
rabbitmq 16:35:09.71 DEBUG ==> Downloading custom plugins...

Thanks for the proposed workaround @mentlak0, we appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

from charts.

The same issue after some digging:
/opt/bitnami/rabbitmq/plugins is under root:root permission even volumePermissions.enable = true not change it
so when we specify communityPlugins rabbitmq try download and put plugin into this directory and don't have permission with exitCode: 23

from charts.