Epic Goal

Build controller (BuildConfigs) uses Kubernetes user namespace in order to run OpenShift build pods in the user namespaces

Why is this important?

To enable any authenticated user on OpenShift to run image builds through BuildConfigs without requiring additional privileges (e.g. builder service account) for OpenShift build pods that are not available to all authenticated users and all pods.

Acceptance Criteria

• Build pods can run in the user namespace using the Kubernetes user namespaces
• Build pods can run with the default service account and the user-namespace-aware equivalent of "restricted" SCC