Add freely configurable securityContext to deployment
What does this MR do?
This MR adds the securityContext for the pod, the init container and the main container. With the default values it uses the same users like the former deployment. It adds a bit of default values for the init container and the main container in order to make the deployment more secure. This is not a breaking change but embeds security best practices.
Why was this MR needed?
To make the Gitlab Runner deployment more secure.
What's the best way to test this MR?
Roll out the chart to a Kubernetes cluster and register the runner with a Gitlab instance.
What are the relevant issue numbers?
I'm not sure what your procedure is for bumping versions on charts but it looks to me like it's something the maintainers do. If you need any more input from my side, please comment. Thank you very much.
Edited by Thilo