podSecurityContext.runAsUser needs to be nulled as well for Openshift

[mephinet]

Currently, the Openshift example does not remove runAsUser completely. When deploying the chart in Openshift, this results in the error:

unable to validate against any security context constraint: [spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000: must be in the ranges: [1000630000, 1000639999]]

To verify without Openshift, you see that

$ helm template -f elasticsearch/examples/openshift/values.yaml elasticsearch elasticsearch/ | grep runAsUser

sets the UID, which is not allowed by the default Openshift security context.

This pull request fixes the example so that runAsUser is not set at all.

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[cla-checker-service]

💚 CLA has been signed

[jmlrt]

LGTM⛴

[jmlrt]

Hi @mephinet,
Thanks for your PR.
Can you sign the CLA: https://www.elastic.co/contributor-agreement

[mephinet]

Hi @jmlrt , I already signed the CLA 3 times... ?

[jmlrt]

backported to 6.8, 7.8and 7.x branches