Mattermost v7.9.1 team-edition helm deployment issues

Troubleshooting
21

For the sake of completeness, the same can be used to resolve a problem fetching profile pictures, etc… from the data directory:

extraInitContainers:
  - command:
      - sh
      - '-c'
      - chown -R 2000:2000 /client/plugins
    image: busybox
    name: changeowner-plugins
    volumeMounts:
      - mountPath: /client/plugins
        name: mattermost-plugins
  - command:
      - sh
      - '-c'
      - chown -R 2000:2000 /data
    image: busybox
    name: changeowner-data
    volumeMounts:
      - mountPath: /data
        name: mattermost-data
1 Like
22

@agnivade is that how it’s supposed to be or are we overseeing something here?

23

Sorry, there seems to be various things being discussed here. How can I help?

24

The main problem seems to be that the filesystem permissions in the application containers, especially /client/plugins, /plugins and obviously also some parts below /data do not seem to be writeable by the pods and someone came up with the idea to start a sidecar container to fix that during initialization, but I don’t believe that this is the only way to fix permission issues. Not sure what needs to be done here in order for the permissions to be set correctly in such a deployment scenario and since you’re experienced with the k8s environment I pinged you for help.

25

Ah well, you got the wrong person here :stuck_out_tongue: Let me bring this to the attention of our cloud platform team.

1 Like
26

Sorry man - and thanks for forwarding.

27

Hello,

Thank you @michaelkoelle for the workaround. Unfortunaly it didn’t work for me, my initcontainer has not the right to modify permission of the folder /client/plugin. I hope this issue will be resolved by mattermost. I encounter the problem since I started the depolyment in my compagny with version 7.7.0

28

Hello, Any news about this problem ?

29

hey, i just try to debug with the same issues you face. i was trying to run with this config:

image
image1228×236 24.6 KB

but it was still will be security issues, i’ve change with the user included on container perhaps there will be some changes from the team to solve this.