# Unhealthy Connect Loop - Confluent for Kuberenetes Quickstart

**URL:** <https://forum.confluent.io/t/unhealthy-connect-loop-confluent-for-kuberenetes-quickstart/2533>\
**Category:** Ops\
**Created:** [19 August 2021 10:04 UTC](https://forum.confluent.io/t/unhealthy-connect-loop-confluent-for-kuberenetes-quickstart/2533 "2021-08-19T10:04:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dcguim](https://avatars.discourse-cdn.com/v4/letter/d/c0e974/32.png) [@dcguim](https://forum.confluent.io/u/dcguim)\
**Post date:** [19 August 2021 10:04 UTC](https://forum.confluent.io/t/unhealthy-connect-loop-confluent-for-kuberenetes-quickstart/2533/1 "2021-08-19T10:04:58Z")

</div>

I am currently trying to install all of the confluent services to our Kubernetes cluster, following this tutorial: [Confluent for Kubernetes Quickstart | Confluent Documentation](https://docs.confluent.io/operator/current/co-quickstart.html)  
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:

```auto
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:6.1.0.0" 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](https://github.com/confluentinc/cp-helm-charts/blob/3ffbdf93dad1baf8a3c9a58a92b8e44bb848cd1c/charts/cp-kafka-connect/values.yaml#L124-L135) 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.

---

<div class="post-metadata">

**Author:** ![dcguim](https://avatars.discourse-cdn.com/v4/letter/d/c0e974/32.png) [@dcguim](https://forum.confluent.io/u/dcguim)\
**Post date:** [24 August 2021 09:44 UTC](https://forum.confluent.io/t/unhealthy-connect-loop-confluent-for-kuberenetes-quickstart/2533/2 "2021-08-24T09:44:14Z")

</div>

Just to mention that I did not experience the same problem in the Connect service using the [github helm charts](https://github.com/confluentinc/cp-helm-charts/tree/3ffbdf93dad1baf8a3c9a58a92b8e44bb848cd1c).

---

<div class="post-metadata">

**Author:** ![rohit2b](https://avatars.discourse-cdn.com/v4/letter/r/9f8e36/32.png) [@rohit2b](https://forum.confluent.io/u/rohit2b)\
**Post date:** [24 August 2021 18:50 UTC](https://forum.confluent.io/t/unhealthy-connect-loop-confluent-for-kuberenetes-quickstart/2533/3 "2021-08-24T18:50:49Z")

</div>

Hi - there’s a few things to look at.

Does Kafka come up with no errors?  
Does `$kubectl logs kafka-0` show any errors?  
Does `$kubetl get pods` show Kafka pods as 3/3 (assuming you are running 3 brokers?

If Kafka is up, then It could be that the Connect containers need more time to pass their health checks. This is how you can change that in any component CustomResource:

```auto
kind: Connect
...
spec:
  replicas: 1
  ...
  podTemplate:
    resources:
      requests:
        cpu: 2000m
        memory: 8Gi
    probe:
      liveness:
        periodSeconds: 10
        failureThreshold: 5
        timeoutSeconds: 500

```