Files
deprecated-helm-charts/stable
Jacob LeGrone 63653fd596 Make jenkins master pod security context optional (#6122)
Cluster configurations may include mutating admission controllers which
dynamically add security contexts to pods and containers.

OpenShift uses this pattern to implement required uid ranges that
differ on a per-namespace basis, and OpenShift's security admission
plugin rejects any pods that make runAsUser requests outside of that
valid uid range.

Removing the securityContext field from the Jenkins pod spec allows the
OpenShift security admission plugin to assign a uid in the correct
range to each container in the pod on behalf of the user, avoiding the
need to provide helm with a different runAsUser value for each
namespace in which Jenkins is deployed.
2018-07-01 12:39:18 -07:00
..
2018-07-01 08:51:17 -07:00
2018-06-24 07:35:03 -07:00
2018-05-17 13:46:51 -07:00
2018-06-25 11:58:22 -07:00
2018-06-25 08:38:02 -07:00
2018-06-26 10:18:52 -07:00
2018-06-05 05:57:13 -07:00
2018-04-30 12:08:36 -07:00
2018-07-01 09:17:17 -07:00