Skip to content

Commit 6cccb7e

Browse files
max-pfeiffertuunit
authored andcommitted
Made the password usage for Redis sub chart more clear
1 parent 2e4cf2f commit 6cccb7e

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

helm/oauth2-proxy/values.yaml

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -363,7 +363,8 @@ sessionStorage:
363363
existingSecret: ""
364364
# Redis password value. Applicable for all Redis configurations. Taken from redis subchart secret if not set. `sessionStorage.redis.existingSecret` takes precedence
365365
password: ""
366-
# Key of the Kubernetes secret data containing the redis password value
366+
# Key of the Kubernetes secret data containing the redis password value. If you use the redis sub chart, make sure
367+
# this password matches the one used in redis.global.redis.password (see below).
367368
passwordKey: "redis-password"
368369
# Can be one of standalone|cluster|sentinel
369370
clientType: "standalone"
@@ -395,6 +396,11 @@ redis:
395396
enabled: false
396397
# Redis specific helm chart settings, please see:
397398
# https://github.com/bitnami/charts/tree/master/bitnami/redis#parameters
399+
# global:
400+
# redis:
401+
# password: yourpassword
402+
# If you install Redis using this sub chart, make sure that the password of the sub chart matches the password
403+
# you set in sessionStorage.redis.password (see above).
398404
# redisPort: 6379
399405
# architecture: standalone
400406

0 commit comments

Comments
 (0)