Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[kubernetes] Kubernetes integration submits high volume of queries for events #3381
**Output of the info page **
Additional environment details (Operating System, Cloud provider, etc):
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
We're queuing some work around this, expect it for 5.14.1 - in the meantime downgrading to 5.13.2 should reduce the load.
Sorry for the trouble.
referenced this issue
Jun 14, 2017
I reworked the kube service matching logic to only pool the apiserver every 5 minutes. That means the kube_service tagging might lag behind a few minutes on creation/deletion but will greatly reduce the traffic. This timing can be configured via the
Could you please try running the
Does it still use the
Unfortunately, as we do the pod -> service mapping on the agent-side, every agent needs this information, that the kubelet does not store.
If you don't use the kube_service tag, we can introduce a configuration option to disable it. The kube_deployment / kube_daemonset / kube_task tags would still work as they only rely on node-local information. Would that work for you?