livenessProbe behavior change Kafka-Connect 0.45.0 vs 0.46.1

[rao2100]

I noticed that in strimzi 0.45.0 when kafka goes down (uninstalled). Kafka-Connect wont restart, though you will see connection errors in the logs.

In strimzi 0.46.1 Kafka-Connect fails livenessProbe and keeps restarting when kafka is uninstalled.

Is this expected behavior? Both using the same config, i did not specify liveness/readiness config for Kafka-Connect.

I there a configuration i can set to make Kafka-Connect not restart when this happens? Just extend the liveness probe?

[scholzj]

The change in behavior is likely related to https://github.com/strimzi/proposals/blob/main/089-adopt-connect-health-endpoint.md? Not really sure if this was intentional / concious change in Strimzi. And withotu any logs I'm not sure how intentional it is on Kafka itself. But Connect is not really working in such a state, so I don't think having it crashloop is a major problem per-se.