Open arpan57 opened 3 months ago
@arpan57
Thanks to notify me about this issue :)
As you reported, valkey/valkey:7.2.5-alpine3.19
has no configurations and supports about cluster.
I will going to further investigate about this issue.
Thanks :)
Thanks @DPS0340
Hello @DPS0340,
Thank you for work on this area. I am trying to make valekey cluster run on the k8s and searching for an patched redis operator or a new operator, came across your git repo.
I cloned the repo and executed ./01-install.sh successfully on the minikube on macbook. What I noticed is the image which has been used in the
redis-operator-0.18.0/custom-resources/redis-cluster.yaml
is for the single instance. Currently, using the operator, I noticed it spawns 6 pods ( 3 leaders+3 followers) but when I try to execute any cluster related commands it fails. (because this operator is using the image for redis-instance)I tried modifying the image and pass the appropriate environment values, and try creating the Valkey cluster. Notice here I am setting the image to
bitnami/valkey-cluster
For example :and in the values.yaml setting environment variables, which we figured out using the pod's logs.
But from here on the pod is stuck in liveliness probe failure resulting in FailedScheduling state.
Warning Unhealthy 2m9s (x4 over 3m9s) kubelet Liveness probe failed: Could not connect to Valkey at valkey-test-leader-0:6379: Connection refused
k logs valkey-test-leader-0
Did you have any success running the valkey cluster with this or any other operator or any guidelines how we can patch further to make it work for valkey-cluster?
Thanks.