Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upKubernetes nodes scrape problems #3948
Comments
This comment has been minimized.
This comment has been minimized.
|
It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided. |
brian-brazil
closed this
Mar 12, 2018
This comment has been minimized.
This comment has been minimized.
|
I reply to myself, the issue was because I forget to taint the kubernetes master and the node-exporter pod was unable to run on a master node without taint! |
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
felixPG commentedMar 12, 2018
•
edited
Hi:
After working with a kubernetes cluster since 3 months with prometheus without problems, today scrape does not work in one node (master kubernetes node), is work for little metrics, an other metrics does not work.
Example:
For kube_node_labels metric the node appear to be scraped:
But for node_uname_info, node_boot_time, node_time cant see the IP of the node, in this case, should be 192.168.133.17 for ietsmartc09spre
I dont know what happend with this, all was working ok until today!
Thanks in advance!