Concerning health checks for rabbitmq connector, could we add a configuration to disable the liveness checks only?
It is currently possible to disable both checks, and since #2326, it is also possible to disable a readiness check, using "health-readiness-enabled". But I did not find any option to disable the liveness check without disabling the readiness check ?
The use case is that in a Kubernetes application (a Quarkus application in my context), I thought that it was better to put checks to external systems only in the readiness check, so that pods are not restarted repeatedly if the external system is down, but only considered as "not ready".
Hello,
Concerning health checks for rabbitmq connector, could we add a configuration to disable the liveness checks only? It is currently possible to disable both checks, and since #2326, it is also possible to disable a readiness check, using "health-readiness-enabled". But I did not find any option to disable the liveness check without disabling the readiness check ?
The use case is that in a Kubernetes application (a Quarkus application in my context), I thought that it was better to put checks to external systems only in the readiness check, so that pods are not restarted repeatedly if the external system is down, but only considered as "not ready".