[bitnami/sonarqube] Fix issue with volume-permissions

bitnami/sonarqube/CHANGELOG.md

@@ -1,8 +1,12 @@
 # Changelog
 
-## 5.2.3 (2024-06-07)
+## 5.2.4 (2024-06-13)
 
-* [bitnami/sonarqube] Release 5.2.3 ([#27046](https://github.com/bitnami/charts/pull/27046))
+* [bitnami/sonarqube] Fix issue with volume-permissions ([#27113](https://github.com/bitnami/charts/pull/27113))
+
+## <small>5.2.3 (2024-06-07)</small>
+
+* [bitnami/sonarqube] Release 5.2.3 (#27046) ([782bb3d](https://github.com/bitnami/charts/commit/782bb3d541d6af79131086d84241aacc23dafe4c)), closes [#27046](https://github.com/bitnami/charts/issues/27046)
 
 ## <small>5.2.2 (2024-06-05)</small>
 

bitnami/sonarqube/Chart.yaml

@@ -37,4 +37,4 @@ maintainers:
 name: sonarqube
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/sonarqube
-version: 5.2.3
+version: 5.2.4

bitnami/sonarqube/README.md

@@ -484,6 +484,7 @@ As an alternative, this chart supports using an initContainer to change the owne
 | `volumePermissions.image.pullSecrets`                       | OS Shell + Utility image pull secrets                                                                                                                                                                                                                 | `[]`                       |
 | `volumePermissions.resourcesPreset`                         | Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if volumePermissions.resources is set (volumePermissions.resources is recommended for production). | `none`                     |
 | `volumePermissions.resources`                               | Set container requests and limits for different resources like CPU or memory (essential for production workloads)                                                                                                                                     | `{}`                       |
+| `volumePermissions.containerSecurityContext.enabled`        | Enable init container's Security Context                                                                                                                                                                                                              | `true`                     |
 | `volumePermissions.containerSecurityContext.seLinuxOptions` | Set SELinux options in container                                                                                                                                                                                                                      | `{}`                       |
 | `volumePermissions.containerSecurityContext.runAsUser`      | Set init container's Security Context runAsUser                                                                                                                                                                                                       | `0`                        |
 

bitnami/sonarqube/templates/deployment.yaml

@@ -183,7 +183,6 @@ spec:
           volumeMounts:
             - name: sonarqube
               mountPath: /bitnami/sonarqube
-              subPath: data
             - name: empty-dir
               mountPath: /tmp
               subPath: tmp-dir

bitnami/sonarqube/values.yaml

@@ -943,13 +943,15 @@ volumePermissions:
   resources: {}
   ## Init container Container Security Context
   ## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
+  ## @param volumePermissions.containerSecurityContext.enabled Enable init container's Security Context
   ## @param volumePermissions.containerSecurityContext.seLinuxOptions [object,nullable] Set SELinux options in container
   ## @param volumePermissions.containerSecurityContext.runAsUser Set init container's Security Context runAsUser
   ## NOTE: when runAsUser is set to special value "auto", init container will try to chown the
   ##   data folder to auto-determined user&group, using commands: `id -u`:`id -G | cut -d" " -f2`
   ##   "auto" is especially useful for OpenShift which has scc with dynamic user ids (and 0 is not allowed)
   ##
   containerSecurityContext:
+    enabled: true
     seLinuxOptions: {}
     runAsUser: 0
 ## @section Sysctl Image parameters