Allow securityContext and podSecurityContext to be configurable via helm parameters

[vepatel]

Expose the securityContext resource to be fully configured via helm. Currently we use this approach to expose the resources configuration of the pod. This will mean changing the securityContext fields in the deployment and daemonset from being hardcoded to being a toYaml representation of the values file, e.g:

securityContext:
          {{- toYaml .Values.controller.securityContext | nindent 10 }}

and we can reference the securityContext and podSecurityContext schemas in our values schema.

This seems to be a common approach in other charts and allows the user full control over the resource, which still allowing us to deliver our current default values. As we do this it also makes sense to expose the podSecurityContext in the same way even though we do not currently use it.

[github-actions]

Hi @vepatel thanks for reporting!

Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂

Cheers!