Allow to configure securityContext for che-gateway container about che HOT 6 OPEN

For some reason I had assumed this was resolved in eclipse-che/che-operator@b9d8ce3 but that does not seem to be the case.

It seems like eclipse-che/che-operator@1bd44bd needs to be extended to allow setting the securityContext for the che-gateway container.

If we are going to work on this feature, it seems like it'd make sense for either @mkuznyetsov or me to work on it since our PR's are closely related to this work.

from che.

More context: DWO uses the configured container SecurityContext when generating containers for a flattened devfile but this SecurityContext is not applied to containers coming from the DevWorkspaceRouting.

from che.

This could also be considered a DWO bug; since the gateway container is added in a separate step (i.e. it comes from the devworkspace routing object and is created by the Che Operator) it might be getting missed in DWO's adding of security context.

I think it might make more sense to fix it in DWO if possible.

from che.

@amisevsk
What do you think?

from che.

Hello @amisevsk, @AObuchow.
Is there any update on this request?

from che.

@karatkep no updates thus far, unfortunately. This issue needs to be prioritized accordingly, and I am currently working on some other tasks, however I will bring it up to the team this coming week for discussion.

from che.