Enable staticID feature to allow constant sentinel ids

After 2 redis pods failure or if worker nodes are restarted, sentinel not able to elect master.

This feature was added with PR: helm/charts#19059

Sentinels never forget about replicas of a given master, even when they are unreachable for a long time.
In Kubernetes, unless specified, each pod is given a random IP. In our case, with 2 slaves and one master, each replicas is attributed to a random IP. Holding on to old replicas IPs will only make it impossible for other sentinels to elect a new master. constant sentinel ID will allow other sentinel peers to update to the new given IP.

Author: manisha-tanwar

values.yaml

@@ -547,6 +547,10 @@ redis:
   # ## https://github.com/bitnami/charts/tree/master/bitnami/redis#master-slave-with-sentinel
   sentinel:
     enabled: true
+    ## Enable or disable static sentinel IDs for each replicas
+    ## If disabled each sentinel will generate a random id at startup
+    ## If enabled, each replicas will have a constant ID on each start-up
+    ##
     staticID: true
   networkPolicy:
     enabled: false