Local health check for helm

[TJM]

Related to #121 - I have been using some terraform code to deploy consul-esm using a kubernetes_deployment to our cluster. It is "generally" working, but when I was first setting it up, I realized that we need some "health checking" for consul-esm itself. I would equate this to a "liveness-probe" and/or "readiness-probe" ... i.e. how can I check to make sure that consul-esm itself is working.

[TJM]

IS there some sort of internal command or http request or "file" we can inspect to see that consul-esm is working from inside the container?

[tristanmorgan]

Consul-esm does have a liveliness indicator in Consul's service discovery.

[TJM]

Consul-esm does have a liveliness indicator in Consul's service discovery.

I don't know if liveness/readiness probes will connect to other containers, but then we have to deal with authentication. I was hoping for something simple and local to the consul-esm container. However, I do think that what you have provided will suffice for the "what happens if consul-esm dies" as that should turn red/unavailable. Then, of course it is something else's responsibility to monitor that and alert as necessary ;). I was looking for something that would end up in the helm chart (deployment) as a local health check. Perhaps a "defacto" /healthz HTTP GET? :-/

[eikenb]

Converting this to a feature request and updating the title to match.