Fails to install on OCP/OKD due to scc violations

[kaplan-michael]

Describe the bug
Fix SCC for OCP/OKD

To Reproduce
Install via helm and set

ocpCompatibility:
  enabled: true

scc fails

would violate PodSecurity "restricted:v1.24": allowPrivilegeEscalation != false (containers "postgres-upgrade", "postgres-init", "postgres", "yugaware" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (containers "postgres-upgrade", "postgres-init", "postgres", "yugaware" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or containers "postgres-upgrade", "postgres-init" must set securityContext.runAsNonRoot=true), seccompProfile (pod or containers "postgres-upgrade", "postgres-init", "postgres", "yugaware" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")

Expected behavior
Installs/deals with scc automatically.

Additional context
Can be worked around by oc adm policy add-scc-from-user anyuid -z <installed-svc-account-name> -n <namespace>

[bhavin192]

@kaplan-michael can you try with following set as well?

securityContext:
  enabled: false

See https://github.com/yugabyte/charts/blob/b8aa3c46b3f020eeed206262233dcb12aa0106cf/stable/yugaware/openshift.values.yaml#L33 for reference. We rely mostly on OpenShift to set correct values of runAsUser, runAsGroup etc.

Do you have restricted SCC enabled in your cluster? Because in our clusters the line you shared shows up as a warning and not as error.

cc @baba230896