-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/kafka] How to define healthcheck for kafka container #75323
Comments
Hi! In the helm chart we have two checks: liveness: exec:
command:
- pgrep
- -f
- kafka readiness: tcpSocket:
port: client So, for your case, you can try mimicking something similar in the container. |
Is it really useful to check for a running process that is PID 1 ? Something is really strange with Bitnami images because the initialization is not working/the container is not starting up if a HEALTHCHECK is enabled ... |
In the case of the readiness I imagine that it does some sort of operation close to a |
Hmmm, I think that just opening a connection to Kafka is not enough to make sure that the service is correctly working. Anyways, as already discussed in #75322 - something is really wrong with the Bitnami images because activating the Docker healthcheck is killing the whole functionality of the container... |
hi @apachler let me check it and investigate a little bit, I will come back as soon as possible with some info. Thanks |
I agree. My kafka pod is stuck where the readiness probe is failing, but the liveliness probe is okay. |
Name and Version
bitnami/kafka:3.7
What is the problem this feature will solve?
I am using 3 instances of Kafka controlled by 3 instances of Zookeeper.
It seems the following healthcheck is not working if used in docker compose.
Since i am not very familiar with Kafka I just wanted to know what healthcheck command should be used.
What is the feature you are proposing to solve the problem?
Container image maintainers should provide a working healthcheck command.
The text was updated successfully, but these errors were encountered: