Add readiness/liveness probe to Daemonset

Open noqcks opened this issue 6 years ago • 1 comments

Hi there,

We're ran into a case where the LogDNA Daemonset has issues connecting to api.logdna.com. In this case the pod will continue to run as normal. The only way we know if something it wrong is when we check our logs and see that nothing has been logging from a node for a couple days.

It would be excellent if the kubernetes manifests had a readiness/liveness probe that was would fail if LogDNA agent cannot connect to api.logdna.com OR it didn't stop attempting to make a connection. (The above image shows it only trying for 4 mins)

Aug 29 '19 17:08 noqcks

@beefcheeks can I work on this one... ?

May 08 '23 04:05 Ambarish07