Open rouke-broersma opened 1 year ago
The best will be to implement either :
@tchiotludo I'm not much of a Java developer, but shouldn't this exception simply crash the application since there's currently no way akhq recovers from this? Or the exception should be caught, and the process should be auto-restarted. The current way leaves akhq functionally broken but still running. There's no button to get it back to a working state either.
For example:
The UI then shows this message:
However the pods report as being perfectly happy:
A restart of the pod fixes the issue. Kafka also isn't unavailable, it's only akhq having trouble reconnecting (probably because the background thread that's supposed to do this has crashed and is not restarting).
Functioning health checks would have us back online, now we have to manually restart the pods. We are using your helm chart, are we missing some configuration option to make the health check behave in the expected manner?