The kvrocks cluster is not creating and ending up with log "kvrocks/kvrocks-cluster-1-demo","caller":"controllers/kvrocks_controller.go:143","msg":"reconcile begin"}"

[parthabls]

I am trying to create a kvrocks cluster in a 4 node kubernetes cluster and whenever I apply the cluster.yaml I see the below logs at kvrocks-operator log.

I also have the etcd statefulset cluster running and which is availble for the kvrock-operator/controller to use. The below log is not sufficeient to make out what's going on. Could you please help me bring the kvrocks cluster.

`2025-10-30T20:49:21.740060333Z stderr F {"level":"info","ts":"2025-10-30T20:49:21Z","logger":"kvrocks/kvrocks-cluster-1-demo","caller":"controllers/kvrocks_controller.go:212","msg":"kvrocks is creating"}
2025-10-30T20:49:21.751964424Z stderr F {"level":"info","ts":"2025-10-30T20:49:21Z","logger":"kvrocks/kvrocks-cluster-1-demo","caller":"controllers/kvrocks_controller.go:143","msg":"reconcile begin"}
2025-10-30T20:49:21.780108756Z stderr F {"level":"info","ts":"2025-10-30T20:49:21Z","logger":"kvrocks/kvrocks-cluster-1-demo","caller":"controllers/kvrocks_controller.go:143","msg":"reconcile begin"}
2025-10-30T20:50:57.175400652Z stderr F {"level":"info","ts":"2025-10-30T20:50:57Z","logger":"kvrocks/kvrocks-cluster-1-demo","caller":"controllers/kvrocks_controller.go:143","msg":"reconcile begin"}`

root@partha-ubuntu-3:~/kvrocks# kubectl get pods --all-namespaces
NAMESPACE       NAME                                         READY   STATUS    RESTARTS   AGE
kruise-system   kruise-controller-manager-67c75dbb45-72gcq   1/1     Running   0          3h58m
kruise-system   kruise-controller-manager-67c75dbb45-mp58r   1/1     Running   0          3h58m
kruise-system   kruise-daemon-9gkdq                          1/1     Running   0          3h49m
kruise-system   kruise-daemon-h4hgm                          1/1     Running   0          3h19m
kruise-system   kruise-daemon-hrt4l                          1/1     Running   0          3h50m
kruise-system   kruise-daemon-sdvtd                          1/1     Running   0          3h58m
kruise-system   kruise-daemon-tb4s9                          1/1     Running   0          3h48m
kube-system     calico-kube-controllers-7498b9bb4c-zgvrf     1/1     Running   0          4h2m
kube-system     calico-node-4wf7v                            1/1     Running   0          3h49m
kube-system     calico-node-bk4kw                            1/1     Running   0          3h50m
kube-system     calico-node-cf6r2                            1/1     Running   0          3h48m
kube-system     calico-node-g6rbc                            1/1     Running   0          4h2m
kube-system     calico-node-j88tl                            1/1     Running   0          3h19m
kube-system     coredns-674b8bbfcf-hwgbv                     1/1     Running   0          4h3m
kube-system     coredns-674b8bbfcf-z8x96                     1/1     Running   0          4h3m
kube-system     etcd-partha-ubuntu-3                         1/1     Running   3          4h3m
kube-system     kube-apiserver-partha-ubuntu-3               1/1     Running   1          4h3m
kube-system     kube-controller-manager-partha-ubuntu-3      1/1     Running   2          4h3m
kube-system     kube-proxy-pzt4r                             1/1     Running   0          3h48m
kube-system     kube-proxy-qz9cc                             1/1     Running   0          3h50m
kube-system     kube-proxy-vzgvm                             1/1     Running   0          3h49m
kube-system     kube-proxy-wvrn8                             1/1     Running   0          4h3m
kube-system     kube-proxy-zsndd                             1/1     Running   0          3h19m
kube-system     kube-scheduler-partha-ubuntu-3               1/1     Running   5          4h3m
kvrocks         etcd-0                                       1/1     Running   0          63s
kvrocks         etcd-1                                       1/1     Running   0          63s
kvrocks         etcd-2                                       0/1     Running   0          63s
kvrocks         kvrocks-operator-controller-manager-qnhfc    2/2     Running   0          3h52m

[parthabls]

It looks like, the latest docker image needs to be updated at hulkdev.

[git-hulk]

@parthabls I have fixed the CI and change the upstream repository to kvrocks/kvrocks-operator, pls have a try again.

[parthabls]

@parthabls I have fixed the CI and change the upstream repository to kvrocks/kvrocks-operator, pls have a try again.

Thanks. I noticed another behaviour, when I applied the cluster.yaml the the kvrocks-operator POD which is in the overlay network didn't respond to kickoff the kvrocks-controller and etcd0-service. But when I just run the kvrocks-operator/main.go on the host which started listening on the 8080 and 8081 port locally on host network and started responding the request made through the cluster.yaml to instantiate the controller and etcd POD in kvrocks name space. Is the kvrocks-operator container should be running in hostNetork = true mode ?