fix: Change security context of Redis image to match redis user

Previously, we set the default security context of the Redis to a user/group not taken. This could cause problems with permissions, resulting in error logs and shutdown delays, thus this commit changes the default user/group to reflect the built-in redis user.

fix #1764

charts/connaisseur/Chart.yaml

@@ -2,8 +2,8 @@ apiVersion: v2
 name: connaisseur
 description: Helm chart for Connaisseur - a Kubernetes admission controller to integrate container image signature verification and trust pinning into a cluster.
 type: application
-version: 2.7.0
-appVersion: 3.7.0
+version: 2.7.1
+appVersion: 3.7.1
 keywords:
   - container image
   - signature

charts/connaisseur/values.yaml

@@ -90,8 +90,8 @@ kubernetes:
       privileged: false
       readOnlyRootFilesystem: true
       runAsNonRoot: true
-      runAsUser: 10001 # remove when using openshift or OKD 4
-      runAsGroup: 20001 # remove when using openshift or OKD 4
+      runAsUser: 999 # redis user id; remove when using openshift or OKD 4
+      runAsGroup: 999 # redis group id; remove when using openshift or OKD 4
       seccompProfile: # remove when using Kubernetes prior v1.19, openshift or OKD 4
         type: RuntimeDefault # remove when using Kubernetes prior v1.19, openshift or OKD 4
     podSecurityContext: {}