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

Proxy: better metrics for failed actions #80061

Open
squeed opened this issue Jul 11, 2019 · 2 comments

Comments

Projects
None yet
4 participants
@squeed
Copy link
Contributor

commented Jul 11, 2019

What would you like to be added:
kube-proxy should expose better metrics around tracking success and failures. Administrators should be able to alert on failure counts.

Why is this needed:
There are several motivating cases:

  • iptables lock contention causes iptables-save to fail at an increasing rate as services + endpoints grows
  • ipvsadm or ipset are failing to execute

Ultimately, there is essentially no feedback from kube-proxy if it fails to program the service network. This makes it annoyingly difficult to debug when things go wrong. As many reasonable hints we can provide should be added.

/sig network

@athenabot

This comment has been minimized.

Copy link

commented Jul 12, 2019

/triage unresolved

Comment /remove-triage unresolved when the issue is assessed and confirmed.

🤖 I am a bot run by vllry. 👩‍🔬

@dgunjetti

This comment has been minimized.

Copy link

commented Jul 16, 2019

is anyone working one this..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.