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)
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.comOR it didn't stop attempting to make a connection. (The above image shows it only trying for 4 mins)