Disable PodSecurityPolicies by default to support Kubernetes 1.25+

PodSecurityPolicies were removed in favour of Pod security standards
that are configured on a cluster or namespace level [1].

[1] https://kubernetes.io/blog/2022/08/25/pod-security-admission-stable/

Change-Id: Ia1e55c09bfad30fd209e96b3eddbda339edc31aa

charts/grafana/grafana.yaml

@@ -4,8 +4,8 @@ rbac:
   create: true
   ## Use an existing ClusterRole/Role (depending on rbac.namespaced false/true)
   # useExistingRole: name-of-some-(cluster)role
-  pspEnabled: true
-  pspUseAppArmor: true
+  pspEnabled: false
+  pspUseAppArmor: false
   namespaced: false
   extraRoleRules: []
   # - apiGroups: []

charts/loki/loki.yaml

@@ -144,7 +144,7 @@ podManagementPolicy: OrderedReady
 
 rbac:
   create: true
-  pspEnabled: true
+  pspEnabled: false
 
 readinessProbe:
   httpGet:

charts/prometheus/prometheus.yaml

@@ -4,7 +4,7 @@ rbac:
   create: true
 
 podSecurityPolicy:
-  enabled: true
+  enabled: false
 
 imagePullSecrets:
 # - name: "image-pull-secret"

charts/promtail/promtail.yaml

@@ -52,7 +52,7 @@ podAnnotations:
 
 rbac:
   create: true
-  pspEnabled: true
+  pspEnabled: false
 
 readinessProbe:
   failureThreshold: 5