Closed arpan57 closed 1 week ago
Not sure what makes your minikube cluster special... Our CI tests the charts on every release, so this default scenario is covered...
I also tested it on a kind cluster and it worked as expected. The cluster is formed.
helm install my-release oci://registry-1.docker.io/bitnamicharts/valkey-cluster --version 0.1.9
You are using Apple silicon, not sure if there is some sort of emulation active for the minikube VM that could interfere. Also, please make sure there is inter-pod communication:
kubectl exec -it my-release-valkey-cluster-0 -- valkey-cli -h <SOME_OTHER_POD_IP> ping
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Thanks. I think this issue came in only on one laptop. On the other it worked ok.
Name and Version
bitnami/valkey-cluster
What architecture are you using?
None
What steps will reproduce the bug?
helm install my-release oci://registry-1.docker.io/bitnamicharts/valkey-cluster
The pods look like this
Pod description/events look like following:
When I tried to connect it using the valkey-cli I notice that it shows only one node (itself) as the part of the cluster.
The pod logs look like this :
What am I missing? Any guidelines on debugging further?
Thanks.
Are you using any custom parameters or values?
No parameters used. only going with
helm install my-release oci://registry-1.docker.io/bitnamicharts/valkey-cluster
What is the expected behavior?
valkey-cluster should be up and pods should be running with ready state 0/1 Using valkey-cli we should be able to list all the nodes
What do you see instead?
Additional information
No response