feat: added minReadySeconds parameter

Author: mojixcoder

README.md

@@ -15,6 +15,7 @@ This repository contains Redis cluster helm charts that can survive pod restarts
 `redis.port` | Redis server port | `6379`
 `redis.bus` | Redis cluster bus port | `16379`
 `redis.resources` | The resources of the redis container | `{}`
+`redis.minReadySeconds` | minimum number of seconds for which a newly created Pod should be running and ready without any of its containers crashing, for it to be considered available | `10`
 `cluster.init` | A boolean to specify whether the cluster should be initialized. (Can be false when cluster is already created and maybe you just want to change the resources of the cluster) | `true`
 `cluster.master` | Number of master nodes | `3`
 `cluster.replicas` | Number of replicas of each master | `1`

templates/statefulset.yaml

@@ -9,6 +9,9 @@ spec:
     matchLabels: {{ include "redis-cluster.labels" . | nindent 6 }}
   serviceName: {{ include "redis-cluster.name" . }}-headless
   replicas: {{ include "redis-cluster.replicaCount" . }}
+  {{- if .Values.redis.minReadySeconds }}
+  minReadySeconds: {{ .Values.redis.minReadySeconds }}
+  {{- end }}
   template:
     metadata:
       labels: {{ include "redis-cluster.labels" . | nindent 8 }}

values.yaml

@@ -1,10 +1,11 @@
-nameOverride: redis-cluster
-fullnameOverride: redis-cluster
+nameOverride: ""
+fullnameOverride: ""
 
 redis:
   image: redis:7.2.3
   port: 6379
   bus: 16379
+  minReadySeconds: 0
 
 cluster:
   init: true