[bitnami/valkey] feat: ✨ 📝 Allow password update via values.yaml (#30690)

* [bitnami/valkey] feat: ✨ 📝 Allow password update via values.yaml

Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com>

* Update CHANGELOG.md

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

---------

Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>

bitnami/valkey/CHANGELOG.md

@@ -1,8 +1,12 @@
 # Changelog
 
-## 2.0.2 (2024-10-30)
+## 2.1.0 (2024-11-29)
 
-* [bitnami/valkey] Fix default kukbectl.command when sentinel.service.createPrimary is true ([#30090](https://github.com/bitnami/charts/pull/30090))
+* [bitnami/valkey] feat: :sparkles: :memo: Allow password update via values.yaml ([#30690](https://github.com/bitnami/charts/pull/30690))
+
+## <small>2.0.2 (2024-11-04)</small>
+
+* [bitnami/valkey] Fix default kukbectl.command when sentinel.service.createPrimary is true (#30090) ([4bd6eb5](https://github.com/bitnami/charts/commit/4bd6eb5ffffb92361dd929289ee17430c815e87e)), closes [#30090](https://github.com/bitnami/charts/issues/30090)
 
 ## <small>2.0.1 (2024-10-29)</small>
 

bitnami/valkey/Chart.lock

@@ -1,6 +1,6 @@
 dependencies:
 - name: common
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 2.26.0
-digest: sha256:5ff7837915aef0067bd32271ee2b10c990774c16c4b6fe0a7c5eb6e53530ce08
-generated: "2024-10-22T22:40:36.006978998Z"
+  version: 2.27.2
+digest: sha256:6fd86cc5a4b5094abca1f23c8ec064e75e51eceaded94a5e20977274b2abb576
+generated: "2024-11-29T17:24:03.100210778+01:00"

bitnami/valkey/Chart.yaml

@@ -36,4 +36,4 @@ maintainers:
 name: valkey
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/valkey
-version: 2.0.2
+version: 2.1.0

bitnami/valkey/README.md

@@ -50,6 +50,13 @@ Bitnami charts allow setting resource requests and limits for all containers ins
 
 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/).
 
+### Update credentials
+
+The Bitnami Valkey 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:
+
+- Run `helm upgrade` specifying a new password in `auth.password`
+- Run `helm upgrade` specifying a new secret in `auth.existingSecret`
+
 ### Prometheus metrics
 
 This chart can be integrated with Prometheus by setting `metrics.enabled` to `true`. This will deploy a sidecar container with [redis_exporter](https://github.com/oliver006/redis_exporter) in all pods and a `metrics` service, which can be configured under the `metrics.service` section. This `metrics` service will have the necessary annotations to be automatically scraped by Prometheus.

bitnami/valkey/templates/secret.yaml

@@ -22,5 +22,5 @@ metadata:
   {{- end }}
 type: Opaque
 data:
-  valkey-password: {{ include "common.secrets.passwords.manage" (dict "secret" (include "common.names.fullname" .) "key" "valkey-password" "providedValues" (list "global.valkey.password" "auth.password") "length" 10 "context" $) }}
+  valkey-password: {{ include "common.secrets.passwords.manage" (dict "secret" (include "common.names.fullname" .) "key" "valkey-password" "providedValues" (list "global.valkey.password" "auth.password") "length" 10 "honorProvidedValues" true "context" $) }}
 {{- end -}}