Storm cluster in Kubernetes - healthchecking approach

[Łukasz Gebel <lu...@gmail.com>]

Hi,

I setup Apache Storm Cluster using Kubernetes. In Kubernetes there are two
types of healthchecks (
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
):

   - liveness - Indicates whether the Container is running. If the liveness
   probe fails, the kubelet kills the Container, and the Container is
   subjected to its restart policy
   <https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy>.
   If a Container does not provide a liveness probe, the default state is


   - readiness - Indicates whether the Container is ready to service
   requests. If the readiness probe fails, the endpoints controller removes
   the Pod’s IP address from the endpoints of all Services that match the Pod.
   The default state of readiness before the initial delay is Failure. If a
   Container does not provide a readiness probe, the default state is
   Success

Can you share your ideas on how to approach such healtchecks in regards to
liveness, readiness probes? Any ideas or practices you use are more than
welcome.

Best regards,
Łukasz