You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: charts/redis/README.md
+9-2
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ Bitnami charts allow setting resource requests and limits for all containers ins
65
65
66
66
To make this process easier, the chart contains the `resourcesPreset` values, which automatically sets the `resources` section according to different presets. Check these presets in [the bitnami/common chart](https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15). However, in production workloads using `resourcePreset` is discouraged as it may not fully adapt to your specific needs. Find more information on container resource management in the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/).
67
67
68
-
### [Rolling VS Immutable tags](https://docs.vmware.com/en/VMware-Tanzu-Application-Catalog/services/tutorials/GUID-understand-rolling-tags-containers-index.html)
68
+
### [Rolling VS Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html)
69
69
70
70
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
71
71
@@ -173,6 +173,13 @@ One way of achieving this is by setting `master.service.internalTrafficPolicy=Lo
173
173
It's recommended to only change `master.count` if you know what you are doing.
174
174
`master.count`greater than `1` is not designed for use when `sentinel.enabled=true`.
175
175
176
+
### Update credentials
177
+
178
+
The Bitnami Redis chart, when upgrading, reuses the secret previously rendered by the chart or the one specified in `auth.existingSecret`. To update credentials, use one of the following:
179
+
180
+
- Run `helm upgrade` specifying a new password in `auth.password`
181
+
- Run `helm upgrade` specifying a new secret in `auth.existingSecret`
182
+
176
183
### Using a password file
177
184
178
185
To use a password file for Redis® you need to create a secret containing the password and then deploy the chart using that secret. Follow these instructions:
@@ -1175,7 +1182,7 @@ This version also introduces `bitnami/common`, a [library chart](https://helm.sh
- secret - String - Required - Name of the 'Secret' resource where the password is stored.
@@ -80,12 +80,15 @@ Params:
80
80
- failOnNew - Boolean - Optional - Default to true. If set to false, skip errors adding new keys to existing secrets.
81
81
- skipB64enc - Boolean - Optional - Default to false. If set to true, no the secret will not be base64 encrypted.
82
82
- skipQuote - Boolean - Optional - Default to false. If set to true, no quotes will be added around the secret.
83
+
- honorProvidedValues - Boolean - Optional - Default to false. If set to true, the values in providedValues have higher priority than an existing secret
83
84
The order in which this function returns a secret password:
84
-
1. Already existing 'Secret' resource
85
+
1. Password provided via the values.yaml if honorProvidedValues = true
86
+
(If one of the keys passed to the 'providedValues' parameter to this function is a valid path to a key in the values.yaml and has a value, the value of the first key with a value will be returned)
87
+
2. Already existing 'Secret' resource
85
88
(If a 'Secret' resource is found under the name provided to the 'secret' parameter to this function and that 'Secret' resource contains a key with the name passed as the 'key' parameter to this function then the value of this existing secret password will be returned)
86
-
2. Password provided via the values.yaml
89
+
3. Password provided via the values.yaml if honorProvidedValues = false
87
90
(If one of the keys passed to the 'providedValues' parameter to this function is a valid path to a key in the values.yaml and has a value, the value of the first key with a value will be returned)
88
-
3. Randomly generated secret password
91
+
4. Randomly generated secret password
89
92
(A new random secret password with the length specified in the 'length' parameter will be generated and returned)
90
93
91
94
*/}}
@@ -106,6 +109,10 @@ The order in which this function returns a secret password:
WARNING: Rolling tag detected ({{ .repository }}:{{ .tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
0 commit comments