-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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
Comments
@a-robinson has the most GKE context on monitoring. |
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. |
ref #14054 |
Is this issue still relevant? |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
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
The text was updated successfully, but these errors were encountered: