Do not specify user id when generate Kubernetes Deployment for Workspace

MR: Pending

Description

When we generate the Kubernetes resources(e.g. Deployment) from the devfile, we explicitly set the user id that it should run as. If memory serves me right, setting the securityContext in the pod configuration was a recommended security practice. However, what point does setting the runAsUser serve? Can we remove it?

Removing it would significantly simplify our documentation which is a mess right now.

Acceptance Criteria

• A decision if we can remove runAsUser attribute of the security context. If the answer is no, the reason for it.
• Can we remove some other attributes as well?

Technical Requirements

TODO: Fill out or delete (optional) [If applicable, please list out any technical requirements for this feature/enhancement.]

Design Requirements

TODO: Fill out or delete (optional) [If applicable, please provide a link to the design specifications for this feature/enhancement.]

Impact Assessment

TODO: Fill out or delete (optional) [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.]

User Story

TODO: Fill out or delete (optional) [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.]