Confluent For Kubernetes: Connect pod going in perpetual restart mode


We have a broker running on an ec2 instance and exposed at (plaintext)

I deployed connect in two different ways:

  1. Deployed helm chart to deploy. a connect pod: Works well. Topics were created on the broker.
  2. Deployed connect pod via CR by utilizing confluent for operator.
    we are trying out confluent-kubernetes-examples/quickstart-deploy at master · confluentinc/confluent-kubernetes-examples · guide to so.
    CRD’s on the operator are installed correctly.

However when i apply following CR:

kind: Connect
  name: connect
  namespace: confluent
  replicas: 1
    application: confluentinc/cp-server-connect-operator:
    init: confluentinc/cp-init-container-operator:
      bootstrapEndpoint: "plaintext://"

i am getting following error message when i describe the pod:

  Type     Reason     Age                   From     Message
  ----     ------     ----                  ----     -------
  Normal   Pulling    6m27s                 kubelet  Pulling image "confluentinc/cp-init-container-operator:"
  Normal   Pulled     5m54s                 kubelet  Successfully pulled image "confluentinc/cp-init-container-operator:" in 33.117379287s
  Normal   Created    5m52s                 kubelet  Created container config-init-container
  Normal   Started    5m52s                 kubelet  Started container config-init-container
  Normal   Pulling    5m50s                 kubelet  Pulling image "confluentinc/cp-server-connect-operator:"
  Normal   Pulled     3m28s                 kubelet  Successfully pulled image "confluentinc/cp-server-connect-operator:" in 2m21.592593165s
  Normal   Created    3m28s                 kubelet  Created container connect
  Normal   Started    3m27s                 kubelet  Started container connect
  Warning  Unhealthy  36s (x12 over 2m26s)  kubelet  Readiness probe failed: Get "": dial tcp connect: connection refused
  Warning  Unhealthy  34s (x6 over 84s)     kubelet  Liveness probe failed: Get "": dial tcp connect: connection refused

Notice the kafka bootstrap endpoint in CR and the error. they are different. looks like CR is not getting applied correctly to connect crd.

Both broker and connect is on same vpc and can talk to each other. i verified it by curl from operator bash to broker.

Any pointers… am i making some obvious mistake?

hmm seems as if the connect container does a self check
on its rest api port (connect rest api defaults to port 8083)

any errors in the logs?