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 scrape not using TLS_config #3855
Comments
This comment has been minimized.
This comment has been minimized.
|
You want the 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
Feb 17, 2018
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.
rikatz commentedFeb 16, 2018
What did you do?
Configured Prometheus to scrape metrics from Kubernetes. But Prometheus keeps returning errors as it cannot auth against the API Server
The following is the config used:
But while using this, the following error is returned:
Note that it seems Prometheus is not using tls_config, and going directly to the API Server (
User: system:anonymous)What did you expect to see?
Scraping from Kubernetes endpoints
What did you see instead? Under which circumstances?
Environment
Linux 3.10.0-514.26.2.el7.x86_64 x86_64