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-ha/Chart.yaml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ keywords:
5
5
- redis
6
6
- keyvalue
7
7
- database
8
-
version: 4.34.11
8
+
version: 4.34.12
9
9
appVersion: 8.2.1
10
10
description: This Helm chart provides a highly available Redis implementation with a master/slave configuration and uses Sentinel sidecars for failover management
Copy file name to clipboardExpand all lines: charts/redis-ha/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,6 +133,7 @@ The following table lists the configurable parameters of the Redis chart and the
133
133
|`redis.livenessProbe.successThreshold`| Success threshold for liveness probe | int |`1`|
134
134
|`redis.livenessProbe.timeoutSeconds`| Timeout seconds for liveness probe | int |`15`|
135
135
|`redis.masterGroupName`| Redis convention for naming the cluster group: must match `^[\\w-\\.]+$` and can be templated | string |`"mymaster"`|
136
+
|`redis.minReadySeconds`| Configure the 'minReadySeconds' parameter to StatefulSet ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#minreadyseconds| int |`0`|
136
137
|`redis.podAnnotations`| Annotations to be added to the redis statefulset pods | object |`{}`|
137
138
|`redis.port`| Port to access the redis service | int |`6379`|
138
139
|`redis.readinessProbe`| Readiness probe parameters for redis container | object |`{"enabled":true,"failureThreshold":5,"initialDelaySeconds":30,"periodSeconds":15,"successThreshold":1,"timeoutSeconds":15}`|
# -- An existing secret containing a key defined by `sentinel.authKey` that configures `requirepass`
531
536
# in the conf parameters (Requires `sentinel.auth: enabled`, cannot be used in conjunction with `.Values.sentinel.password`)
537
+
# Supports templates like "{{ .Release.Name }}-sentinel-creds"
532
538
existingSecret: ""
533
539
534
540
## Defines the key holding the sentinel password in existing secret.
@@ -852,6 +858,7 @@ authSecretAnnotations: {}
852
858
853
859
## Use existing secret containing key `authKey` (ignores redisPassword)
854
860
## Can also store AWS S3 or SSH secrets in this secret
861
+
## Supports templates like "{{ .Release.Name }}-creds"
855
862
# -- An existing secret containing a key defined by `authKey` that configures `requirepass` and `masterauth` in the conf
856
863
# parameters (Requires `auth: enabled`, cannot be used in conjunction with `.Values.redisPassword`)
857
864
existingSecret: ~
@@ -905,7 +912,8 @@ emptyDir: {}
905
912
tls:
906
913
## Fill the name of secret if you want to use your own TLS certificates.
907
914
## The secret should contains keys named by "tls.certFile" - the certificate, "tls.keyFile" - the private key, "tls.caCertFile" - the certificate of CA and "tls.dhParamsFile" - the dh parameter file
908
-
## These secret will be genrated using files from certs folder if the secretName is not set and redis.tlsPort is set
915
+
## Supports templates like "{{ .Release.Name }}-tls"
916
+
## This secret will be generated using files from certs folder if the secretName is not set and redis.tlsPort is set
0 commit comments