Create better Kubernetes liveness, readiness and startup Probes
Opened this issue · 1 comments
Source: #71 (comment)
Probes should be based on the opened ports the app uses. That means, the application to be considered up, running and healthy should, at least:
- Respond to the configured HTTP port. This is a global health check that can also be used for telling K8s the app is not running properly (for example, if we catch some internal errors, etc and we need to stop the execution).
- Respond to the configured Websocket port.
- All Kafka opened ports should be able to respond to a Kafka Metadata Request. This can be made by using kcat or in the worst case, just a simple nc connection test.
This issue has been automatically marked as stale because it has not had recent activity 😴
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Thank you for your patience ❤️