Jose Antonio Carmona

Hi @abhishekgupta2205 The real reason behind this is that the `redis` process does not have enough permissions to write on `var/log/redis.log`. By default, even if the container runs as a...

Sorry, but I can't reproduce it on my side: ```bash $ cat /tmp/custom-values.yaml podSecurityContext: enabled: true fsGroup: 0 runAsUser: 0 containerSecurityContext: enabled: true runAsUser: 0 runAsNonRoot: false $ helm install...

As said in [my previous comment](https://github.com/bitnami/charts/issues/11045#issuecomment-1176356101), `redis` cannot write in those directories by default. You have two options: - Use a path where `redis` has enough permissions to write, such...

> ON upgrading the chart it shows same error Are you upgrading from an older version? On my side, I still cannot reproduce your issue. In order to do so:...

Hi @izturn There are two main reasons for the CI Pipeline to be failing: - The pipeline has detected that your changes break the chart: all the pods do not...

Hi @aslafy-z, sorry for the delay >I think there should also be a sharded version of the storegateway PDB. Would you let me adding it to this PR? Yes, totally!...

Hi @romilpunetha Thanks for reporting the issue! It seems this problem was already addressed in https://github.com/bitnami/charts/pull/11431. Could you please check if it is working for you now?

Hi @sglogger Did you eventually come to a solution? If not I will be happy to help you out 😁. Should you find any other problem, do not hesitate to...

Hey @sglogger I see, thanks for pointing that out! I would like to know a little bit more about the environment on which you are deploying the boostrap cluster. From...

Hi @sglogger I think the main reason behind this is the different networks in which both containers are running and the way this container is configured to retrieve the IPs....