Valters Jansons

Apply UID/GID defaults from image

29

### Proposed changes [`build/Dockerfile` specifies `USER 101` for `common` target](https://github.com/nginxinc/kubernetes-ingress/blob/v3.2.1/build/Dockerfile#L247-L248), which is re-applied into the final images. Helm Chart/Manifests do not need to specify UID explicitly, and can instead use...

### Is there an existing issue for this? - [X] I have searched the existing issues ### Community Note * Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)...

Support OpenShift's built-in `restricted-v2` Security Context Constraint

3

**Is your feature request related to a problem? Please describe.** Security teams prefer referencing default (built-in) security restrictions. In OpenShift (v4.11+) the `restricted-v2` Security Context Constraint is default, and previously...

Setting `inclusive` membership on users is not possible

2

[membership](https://docs.puppet.com/puppet/4.9/types/user.html#user-attribute-membership) can be set on a user and it can specify either that the groups listed is a minimal set or that the groups listed in an inclusive set. There...

Set SCC's `RunAsUser` as `MustRunAsRange`

8

### Proposed changes Upstream Helm Chart is removing explicit `runAsUser` value from the Deployment and DaemonSet resources. This practically means the UID will be inherited from image's Dockerfile. Users on...