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

Unable to scrape kube-controller-manager and kube-scheduler metrics #51

Closed
lnovara opened this issue Oct 12, 2020 · 2 comments
Closed

Unable to scrape kube-controller-manager and kube-scheduler metrics #51

lnovara opened this issue Oct 12, 2020 · 2 comments
Assignees
@lnovara
Labels
bug Something isn't working

Comments

@lnovara
Copy link
Contributor

lnovara commented Oct 12, 2020 •
edited
Loading

Starting from 1.17, kubeadm is not exposing anymore kube-controller-manager and kube-scheduler metrics over the insecure port (respectively TCP/10252 and TCP/10251) this makes our current ServiceMonitor configuration unable to properly scrape such targets.

Refs:
@lnovara lnovara added the bug Something isn't working label Oct 12, 2020
@lnovara lnovara self-assigned this Oct 12, 2020
@lnovara lnovara mentioned this issue Oct 12, 2020
Merged
@angelbarrera92
Copy link
Contributor

Closed with #52

@angelbarrera92
Copy link
Contributor

Thanks for spotting and solve the issue Luca!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lnovara lnovara

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@angelbarrera92 @lnovara