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.

Sign up for GitHub

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

Jump to bottom

don't talk to apiserver and report on k8s objects from all probes #2972

Open
rade opened this issue Dec 8, 2017 · 1 comment
Open

don't talk to apiserver and report on k8s objects from all probes #2972

rade opened this issue Dec 8, 2017 · 1 comment
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality k8s Pertains to integration with Kubernetes performance Excessive resource usage and latency; usually a bug or chore

Comments

@rade
Copy link
Member

rade commented Dec 8, 2017

ATM every probe retrieves the info about all k8s objects. It only reports on local pods, but does fetch info on all pods, and does fetch & report on all controllers.

This is putting unnecessary load on the k8s apiserver, and the probes, and inflates the report sizes.
@rade rade added chore Related to fix/refinement/improvement of end user or new/existing developer functionality k8s Pertains to integration with Kubernetes performance Excessive resource usage and latency; usually a bug or chore labels Dec 8, 2017
@rade
Copy link
Member Author

rade commented Dec 8, 2017

We could have a special, dedicated pod, not part of the scope probe daemonset, for producing a report with just the k8s info. I believe this should "just work" - merging the report with that of the normal probes - now sans k8s info - ought to produce an aggregate report that is the same as what we currently get.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality k8s Pertains to integration with Kubernetes performance Excessive resource usage and latency; usually a bug or chore
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rade