diff --git a/bitnami/sonarqube/CHANGELOG.md b/bitnami/sonarqube/CHANGELOG.md index 5ea5ae77e2d3ae..e332dcbbbf75d2 100644 --- a/bitnami/sonarqube/CHANGELOG.md +++ b/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)) + +## 5.2.3 (2024-06-07) + +* [bitnami/sonarqube] Release 5.2.3 (#27046) ([782bb3d](https://github.com/bitnami/charts/commit/782bb3d541d6af79131086d84241aacc23dafe4c)), closes [#27046](https://github.com/bitnami/charts/issues/27046) ## 5.2.2 (2024-06-05) diff --git a/bitnami/sonarqube/Chart.yaml b/bitnami/sonarqube/Chart.yaml index 70cea09a314a73..c62aaa88e24e64 100644 --- a/bitnami/sonarqube/Chart.yaml +++ b/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 diff --git a/bitnami/sonarqube/README.md b/bitnami/sonarqube/README.md index 09cd0e65e8d946..6af58c6d2039eb 100644 --- a/bitnami/sonarqube/README.md +++ b/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` | diff --git a/bitnami/sonarqube/templates/deployment.yaml b/bitnami/sonarqube/templates/deployment.yaml index 7814c14720dded..aaf9a7b01aa9cc 100644 --- a/bitnami/sonarqube/templates/deployment.yaml +++ b/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 diff --git a/bitnami/sonarqube/values.yaml b/bitnami/sonarqube/values.yaml index e1493395f76b74..3a68bd1c79dc71 100644 --- a/bitnami/sonarqube/values.yaml +++ b/bitnami/sonarqube/values.yaml @@ -943,6 +943,7 @@ 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 @@ -950,6 +951,7 @@ volumePermissions: ## "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