Hardcoded securityContext in gloo-fed apiserver

[lgadban]

Describe the bug
One of the containers in the gloo-fed apiserver deployment contains a hardcoded securityContext with runAsUser set, which is not compatible with running on OCP.

https://github.com/solo-io/solo-projects/blob/master/install/helm/gloo-fed/templates/apiserver-deployment.yaml#L117-L118

To Reproduce

1. Install gloo-fed on OCP

Error creating: pods "gloo-fed-console-6c6b66f968-" is forbidden: unable to validate against any security context constraint: [spec.containers[2].securityContext.runAsUser: Invalid value: 101: must be in the ranges: [1001810000, 1001819999]]

Expected behavior
A floatingUserId behavior similar to the other gloo deployments

Additional context
N/A

[lgadban]

https://github.com/solo-io/solo-projects/blob/v1.8.0/install/helm/gloo-fed/templates/apiserver-deployment.yaml#L88-L90
https://github.com/solo-io/solo-projects/blob/v1.8.0/install/helm/gloo-fed/templates/apiserver-deployment.yaml#L97-L98
https://github.com/solo-io/solo-projects/blob/v1.8.0/install/helm/gloo-fed/templates/apiserver-deployment.yaml#L120-L121

[chrisgaun]

Similar issue we can close out when this is done most likely #4196