Healthcheck is down when consumers are not running

This is a recent enhancement described in https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1059, more precisely this line of code

I understand the rationale behind it, but this wreaks a bit of havoc in our case : having the listeners not running is a valid case for us.

For example some of our microservices are configured with autoStartup:false and we decide when to start consuming messages based on other factors (the availability of external services needed to process the messages for example)

An another example : we may want to stop the consumption manually (via the POST /actuator/bindings endpoint) for a maintenance operation for example.

Our services are running on Kubernetes, and the liveness probe is now restarting the services in those nominal cases.

A configuration property indicating whether to check if the listener container is running may be a nice way to handle all cases.

[snussbaumer]

Thank you guys for such a quick and relevant response !

[garyrussell]

https://github.com/spring-projects/spring-kafka/pull/1971