setup - chown /usr/share/graylog/data Operation not permitted about charts HOT 4 CLOSED

You can set graylog.podSecurityContext to {} when upgrading.
It will override the new default value.

from charts.

I faced this issue as well and the above workaround did not work for me.
graylog.podSecurityContext sets the securityContext at the pod level, not within the init container, which was what was causing the problem.

Furthermore if helm encounters a dictionary that is overridden by another dictionary it will merge the two, not replace one with the other. Merging a dictionary with {} is a no-op, so setting it as above had no effect.

In order to prevent the securityContext being set in the init container I had to set graylog.securityContext to false

from charts.

I have the same problem. Helm chart version 2.3.6 has the same problem.

'/k8s/kubectl' saved
chown: /usr/share/graylog/data/journal: Operation not permitted
chown: /usr/share/graylog/data/journal: Operation not permitted
chown: /usr/share/graylog/data/: Operation not permitted
chown: /usr/share/graylog/data/: Operation not permitted

As @andrewjmurphy said, when I make securityContext: false, it works properly.

from charts.

I had the same problem.
This solution of @andrewjmurphy worked: graylog.securityContext to false

But how are we going to proceed, @KongZ ... can I put this value in helm, or is there another way to solve it?

from charts.