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

Heapter doesn't collect stats from master node #10891

Closed
dchen1107 opened this issue Jul 7, 2015 · 7 comments
Closed

Heapter doesn't collect stats from master node #10891

dchen1107 opened this issue Jul 7, 2015 · 7 comments
Labels
area/monitoring lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@dchen1107
Copy link
Member

Today heapster is enabled by default for both GKE and GCE for monitoring, but it doesn't collect stats from master node. The reason is master node is never register itself to apiserver. I remembered either me or @vishh filed the issue before. But back then, the decision is we are going to use collectd + GCM as the default solution for both GKE and GCE. But decision was changed later, then I filed #9028.

Now I realized that we missed monitoring on master node for both GKE and GCE. cc/ @brendandburns @alex-mohr @roberthbailey @thockin @vishh @saad-ali

@dchen1107 dchen1107 added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node. team/cluster labels Jul 7, 2015
@dchen1107
Copy link
Member Author

#10760

@alex-mohr
Copy link
Contributor

@a-robinson has the most GKE context on monitoring.

@a-robinson
Copy link
Contributor

We may just have to let GCE and GKE differ here, since heapster won't be able to reach the master's kubelet on GKE. It makes sense to re-add this for GCE, though.

@dchen1107 dchen1107 added this to the v1.0-post milestone Jul 9, 2015
@bgrant0607 bgrant0607 removed this from the v1.0-post milestone Jul 24, 2015
@davidopp
Copy link
Member

ref #14054

@cmluciano
Copy link

Is this issue still relevant?

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 21, 2017
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/monitoring lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

8 participants