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

Liveness probe failed for DaemonSet with host network #676

Open
yaspokoyen opened this issue Mar 19, 2025 · 0 comments
Open

Liveness probe failed for DaemonSet with host network #676

yaspokoyen opened this issue Mar 19, 2025 · 0 comments

Comments

@yaspokoyen
Copy link

When in values set bindIp: true

Liveness probe failed, because it goes to IP addr port (node IP actually).
Simple example:

I have 3 pods with IPs
10.184.0.7
10.184.0.21
10.184.0.13

and liveness probe try to check http://10.184.0.7:8080/health, but needs to check on addr http://169.254.20.10:8080/health

by default, i cannot change addr for check, then i get error

[INFO] SIGTERM: Shutting down servers then terminating

Can you please add possibility to modify host parameter in livenessProbe.http Get

https://github.com/deliveryhero/helm-charts/blob/master/stable/node-local-dns/templates/daemonset.yaml#L95

or maybe i do something wrong. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant