fix: remove non-root which are usually disabled during on-prem install

charts/testkube/values.yaml

@@ -112,8 +112,7 @@ mongodb:
   #      effect: NoSchedule
   # ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
   # -- MongoDB Pod Security Context
-  podSecurityContext:
-    runAsNonRoot: true
+  podSecurityContext: {}
   # For OpenShift clusters use the following settings:
   #  fsGroup: 1000670000
 
@@ -575,8 +574,7 @@ testkube-api:
     resources: {}
     # ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
     # -- MinIO Pod Security Context
-    podSecurityContext:
-      runAsNonRoot: true
+    podSecurityContext: {}
     # ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
     # -- Security Context for MinIO container
     securityContext: {}
@@ -961,8 +959,7 @@ testkube-operator:
     initialDelaySeconds: 3
   # ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
   # -- Testkube Operator Pod Security Context
-  podSecurityContext:
-    runAsNonRoot: true
+  podSecurityContext: {}
   # -- Security Context for manager Container
   securityContext:
     # -- Make root filesystem of the container read-only
@@ -1087,8 +1084,7 @@ testkube-operator:
       labels: {}
       # ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
       # -- kube-webhook-certgen Job Security Context
-      podSecurityContext:
-        runAsNonRoot: true
+      podSecurityContext: {}
 
       # Testkube Operator Service Account parameters
       serviceAccount: