Redis Cluster nodes not connected

After deploying the bitnami redis-cluster helm chart using the default values, my nodes are not connecting to one another. https://artifacthub.io/packages/helm/bitnami/redis-cluster

I'm not sure how to debug this issue and where to begin.

>> kubectl get pods -n cache
NAME              READY   STATUS    RESTARTS      AGE
redis-cluster-0   1/1     Running   1 (13h ago)   22h
redis-cluster-1   1/1     Running   0             22h
redis-cluster-2   1/1     Running   0             22h
redis-cluster-3   1/1     Running   0             22h
redis-cluster-4   1/1     Running   0             22h
redis-cluster-5   1/1     Running   0             22h

>> kubectl get svc -n cache
NAME                     TYPE           CLUSTER-IP       EXTERNAL-IP                                                                        PORT(S)                          AGE
redis-cluster            ClusterIP      172.20.152.249   <none>                                                                             6379/TCP                         22h
redis-cluster-0-svc      LoadBalancer   172.20.140.190   xxx.us-east-1.elb.amazonaws.com    6379:30573/TCP,16379:31743/TCP   22h
redis-cluster-1-svc      LoadBalancer   172.20.131.181   xxx.us-east-1.elb.amazonaws.com    6379:31183/TCP,16379:30334/TCP   22h
redis-cluster-2-svc      LoadBalancer   172.20.233.108   xxx.us-east-1.elb.amazonaws.com    6379:32164/TCP,16379:31787/TCP   22h
redis-cluster-3-svc      LoadBalancer   172.20.43.155    xxx.us-east-1.elb.amazonaws.com   6379:31954/TCP,16379:32035/TCP   22h
redis-cluster-4-svc      LoadBalancer   172.20.230.21    xxx.us-east-1.elb.amazonaws.com   6379:31526/TCP,16379:30265/TCP   22h
redis-cluster-5-svc      LoadBalancer   172.20.80.151    xxx.us-east-1.elb.amazonaws.com   6379:31171/TCP,16379:32167/TCP   22h
redis-cluster-headless   ClusterIP      None             <none>

I have no name!@redis-cluster-0:/$ redis-cli
127.0.0.1:6379> cluster nodes
57414b2efd12d054e32987aefc2a34ff111ab23d redis-cluster-0.internal.lumatax.com:6379@16379 myself,master - 0 0 0 connected
127.0.0.1:6379> cluster info
cluster_state:fail
cluster_slots_assigned:0
cluster_slots_ok:0
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:1
cluster_size:0
cluster_current_epoch:0
cluster_my_epoch:0
cluster_stats_messages_sent:0
cluster_stats_messages_received:0
total_cluster_links_buffer_limit_exceeded:0

Comment From: newbenji

it seem to me its something with pvc to do if i choose persistence.enabled: false they come up correctly

Comment From: newbenji

i will try investigate more after work Using synology csi driver