Skip to content
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

Add readiness/liveness probe to Daemonset #123

Open
noqcks opened this issue Aug 29, 2019 · 1 comment
Open

Add readiness/liveness probe to Daemonset #123

noqcks opened this issue Aug 29, 2019 · 1 comment
Assignees
Labels
help wanted k8s For LogDNA K8s Agent

Comments

@noqcks
Copy link

noqcks commented Aug 29, 2019

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.

image

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)

@smusali smusali added the k8s For LogDNA K8s Agent label Oct 7, 2020
@Ambarish07
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted k8s For LogDNA K8s Agent
Projects
None yet
Development

No branches or pull requests

5 participants