github/deprecated-helm-charts
1
0
Fork 0
mirror of https://github.com/helm/charts.git synced 2026-08-23 22:37:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

[stable/redis] Make volumePermissions init container optional (#11029)

Browse Source 
* [stable/redis] Make volumePermissions init container optional

Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>

* Bump chart to major version

Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>

* Update readme for upgrading

Signed-off-by: Javier J. Salmeron Garcia <jsalmeron@bitnami.com>
This commit is contained in:
Javier J. Salmerón-García
2019-02-05 05:37:52 -08:00
committed by Kubernetes Prow Robot
parent 471f21f11f
commit 55f2637ad7
5 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stable/redis/Chart.yaml
+1 -1
View File
@@ -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:
stable/redis/README.md
+7
View File
@@ -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`.
stable/redis/templates/redis-master-statefulset.yaml
+1 -1
View File
@@ -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 }}
stable/redis/values-production.yaml
+1
View File
@@ -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
stable/redis/values.yaml
+1
View File
@@ -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