mattermost-operator does not provide appropriate configuration for securityContext in mattermost deploymets.

[mattermost]

mattermost-operator does not provide appropriate configuration for securityContext in mattermost deploymets.

[frjaraur]

Many thanks it really worked for me with:

  resourcePatch:
    deployment:
      patch: '[{"op":"add","path":"/spec/template/spec/containers/0/securityContext","value":{"runAsUser": 10001}}]'

[frjaraur]

Sorry, I forgot that neither mattermost-operator nor mattermost instances provide securityContext configurations, I did myself for mattermost operator but it should be added also to mattermost deployments.

[Szymongib]

Hey @frjaraur, thanks for reporting, this came up in the past, and I think we should add it to Mattermost CR.

For now, there exist a workaround with use of resourcePatch, you can find the details here https://community.mattermost.com/core/pl/dricyco3sbn85kacom55mq9zey

[Szymongib]

From the linked thread, you can set it by adding to Mattermost resource:

  resourcePatch:
    deployment:
      patch: '[{"op":"add","path":"/spec/template/spec/initContainers/0/securityContext","value":{"runAsUser": 1337}}]'

Operator needs to be at in version 1.17+ and CRDs need to match this version.

[frjaraur]

Thanks, but it seems it will work for initial containers only or did you just post an example?

[Szymongib]

Ah, yeah, that is just example copied straight from the channel. It should be possible to adjust it according to the needs.

[Szymongib]

We would like to add a native support for securityContext therefore reopening this.