I am currently trying to install all of the confluent services to our Kubernetes cluster, following this tutorial: Confluent for Kubernetes Quickstart | Confluent Documentation
I noticed while provisioning the Connect container on step 3.1 of the tutorial, that a unhealthy loop is triggered.
When inspecting the connect pod:
Normal Created 2m32s kubelet Created container config-init-container Normal Started 2m31s kubelet Started container config-init-container Warning Unhealthy 27s kubelet Readiness probe failed: Get "http://MYIP:8083/v1/metadata/id": dial tcp MYIP:8083: connect: connection refused Warning BackOff 23s (x2 over 25s) kubelet Back-off restarting failed container Normal Pulled 12s (x3 over 2m31s) kubelet Container image "confluentinc/cp-server-connect-operator:126.96.36.199" already present on machine Normal Created 11s (x3 over 2m31s) kubelet Created container connect Normal Started 11s (x3 over 2m31s) kubelet Started container connect
Therefore, I attempted to increase the initial delay in the Connect pod specification. However, it is not clear how to do this on the
io.confluent.platform.v1beta1.Connect.spec. I also noticed that on on the official official connect helm chart the
livenessProbe can be configured. But I didn’t find the same flexibility for
readinessProbe. I will try nevertheless to run the connect helm chart of confluent and compare if results in the same problems as in the Confluent for Kubernetes Quickstart.