diff --git a/stable/redis/Chart.yaml b/stable/redis/Chart.yaml index eb1657b94d..7a0801888a 100644 --- a/stable/redis/Chart.yaml +++ b/stable/redis/Chart.yaml @@ -1,5 +1,5 @@ name: redis -version: 5.5.0 +version: 6.0.0 appVersion: 4.0.12 description: Open source, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. keywords: diff --git a/stable/redis/README.md b/stable/redis/README.md index bbb662c161..7290f48e57 100644 --- a/stable/redis/README.md +++ b/stable/redis/README.md @@ -167,6 +167,7 @@ The following table lists the configurable parameters of the Redis chart and the | `master.readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed (redis master pod) | `1` | | `master.readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `5` | | `master.priorityClassName` | Redis Master pod priorityClassName | {} | +| `volumePermissions.enabled` | Enable init container that changes volume permissions in the registry (for cases where the default k8s `runAsUser` and `fsUser` values do not work) | `false` | | `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` | | `volumePermissions.image.repository` | Init container volume-permissions image name | `bitnami/minideb` | | `volumePermissions.image.tag` | Init container volume-permissions image tag | `latest` | @@ -276,3 +277,9 @@ sysctlImage: sysctl -w net.core.somaxconn=10000 echo never > /host-sys/kernel/mm/transparent_hugepage/enabled ``` + +## Upgrade + +## To 6.0.0 + +Previous versions of the chart were using an init-container to change the permissions of the volumes. This was done in case the `securityContext` directive in the template was not enough for that (for example, with cephFS). In this new version of the chart, this container is disabled by default (which should not affect most of the deployments). If your installation still requires that init container, execute `helm upgrade` with the `--set volumePermissions.enabled=true`. diff --git a/stable/redis/templates/redis-master-statefulset.yaml b/stable/redis/templates/redis-master-statefulset.yaml index af1cf571d9..d2089e4284 100644 --- a/stable/redis/templates/redis-master-statefulset.yaml +++ b/stable/redis/templates/redis-master-statefulset.yaml @@ -152,7 +152,7 @@ spec: - name: config mountPath: /opt/bitnami/redis/etc {{- end }} - {{- $needsVolumePermissions := and ( and .Values.master.persistence.enabled (not .Values.persistence.existingClaim) ) .Values.master.securityContext.enabled }} + {{- $needsVolumePermissions := and .Values.volumePermissions.enabled (and ( and .Values.master.persistence.enabled (not .Values.persistence.existingClaim) ) .Values.master.securityContext.enabled) }} {{- if or $needsVolumePermissions .Values.sysctlImage.enabled }} initContainers: {{- if $needsVolumePermissions }} diff --git a/stable/redis/values-production.yaml b/stable/redis/values-production.yaml index 09d83bcd08..30e87804be 100644 --- a/stable/redis/values-production.yaml +++ b/stable/redis/values-production.yaml @@ -364,6 +364,7 @@ metrics: ## volumePermissions: Change the owner of the persist volume mountpoint to RunAsUser:fsGroup ## volumePermissions: + enabled: false image: registry: docker.io repository: bitnami/minideb diff --git a/stable/redis/values.yaml b/stable/redis/values.yaml index adcb31daba..c6dedfba8f 100644 --- a/stable/redis/values.yaml +++ b/stable/redis/values.yaml @@ -365,6 +365,7 @@ metrics: ## volumePermissions: Change the owner of the persist volume mountpoint to RunAsUser:fsGroup ## volumePermissions: + enabled: false image: registry: docker.io repository: bitnami/minideb