Removing PSC and CSC to improve security

values.yaml

@@ -64,7 +64,7 @@ imagePullSecrets: []
 # Security context is only usable with rootless image due to image design
 ## @param podSecurityContext.fsGroup Set the shared file system group for all containers in the pod.
 podSecurityContext:
-  fsGroup: 1000
+#  fsGroup: 1000
 
 ## @param containerSecurityContext Security context
 containerSecurityContext:
@@ -83,9 +83,9 @@ containerSecurityContext:
   #  type: RuntimeDefault
   privileged: false
   readOnlyRootFilesystem: true
-  runAsGroup: 1000
+  # runAsGroup: 1000
   runAsNonRoot: true
-  runAsUser: 1000
+  # runAsUser: 1000
 
 ## @deprecated The securityContext variable has been split two:
 ## - containerSecurityContext
@@ -185,8 +185,7 @@ ingress:
 ## @section deployment
 #
 ## @param resources Kubernetes resources
-resources:
-  {}
+resources: {}
   # We usually recommend not to specify default resources and to leave this as a conscious
   # choice for the user. This also increases chances charts run on environments with little
   # resources, such as Minikube. If you do want to specify resources, uncomment the following
@@ -227,8 +226,7 @@ priorityClassName: ""
 ## @param deployment.labels Labels for the deployment
 ## @param deployment.annotations Annotations for the Gitea deployment to be created
 deployment:
-  env:
-    []
+  env: []
     # - name: VARIABLE
     #   value: my-value
   terminationGracePeriodSeconds: 60
@@ -397,8 +395,7 @@ gitea:
       tlsConfig: {}
 
   ## @param gitea.ldap LDAP configuration
-  ldap:
-    []
+  ldap: []
     # - name: "LDAP 1"
     #  existingSecret:
     #  securityProtocol:
@@ -415,8 +412,7 @@ gitea:
 
   # Either specify inline `key` and `secret` or refer to them via `existingSecret`
   ## @param gitea.oauth OAuth configuration
-  oauth:
-    []
+  oauth: []
     # - name: 'OAuth 1'
     #   provider:
     #   key: