Allow empty securityContext

[cniackz]

Objective:

Avoid hardcoding values that are not part of any security context constraint and allow Tenant to be deployed without changing scc in OpenShift as Operator logic is currently not allowing empty securityContext for Tenant and this is totally wrong!.

[dnskr]

@cniackz I think there is a similar issue for Prometheus and its init container.
Also unfortunately there is no way to specify security context for Prometheus init container what makes it impossible to use on OpenShift.

operator/pkg/resources/statefulsets/prometheus.go

Lines 207 to 214 in f6c9c8b

	var runAsUser int64
	runAsNonRoot := false
	allowPrivilegeEscalation := true
	initContainerSecurityContext = corev1.SecurityContext{
	RunAsUser: &runAsUser,
	RunAsNonRoot: &runAsNonRoot,
	AllowPrivilegeEscalation: &allowPrivilegeEscalation,
	}

I.e. Prometheus cannot start on OpenShift, because initContainer[0].securityContext.runAsUser is 0.

[cniackz]

Thank you @dnskr but we are deprecating Prometheus for time being. We can open a separate PR for that if this feature comes back again. Or if I am mistaken we can have separate PR for it. For now, let's focus on the Tenant deployment in OpenShift at least.

[cniackz]

All tests passing now!:

[allanrogerr]

LGTM