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

Expose kube-scheduler and kube-controller-manager metrics #4405

Closed
Tracked by #5371
Cajga opened this issue Dec 14, 2022 · 1 comment
Closed
Tracked by #5371

Expose kube-scheduler and kube-controller-manager metrics #4405

Cajga opened this issue Dec 14, 2022 · 1 comment
Assignees
Labels
external An issue, bug or feature request filed from outside the AWS org priority/p1 On the list but not scheduled team/ce
Milestone

Comments

@Cajga
Copy link
Contributor

Cajga commented Dec 14, 2022

What would you like to be added:
We would like to be able to scrape the kube-scheduler and the kube-controller-manager metrics which are important to understand the state of the cluster. Both of these services are exporting Prometheus metrics but by default, we cannot scrape them in EKS Anywhere as these services are only listening on localhost (at least on Bare Metal installations... I do not have EKS-A on other platform to verify this).

A simple way would be to modify the /etc/kubernetes/manifests/kube-scheduler.yaml and the /etc/kubernetes/manifests/kube-controller-manager.yaml files to have --bind-address=0.0.0.0 in them (manually modifying these files on the masters is my workaround at the moment).

Why is this needed:
As mentioned above, these are important metrics to understand the state of the cluster and set up proper alerting/visualisation in a production environment.

@TerryHowe TerryHowe added the external An issue, bug or feature request filed from outside the AWS org label Dec 14, 2022
@g-gaston
Copy link
Member

Thanks for the suggestion @Cajga, we will look into it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external An issue, bug or feature request filed from outside the AWS org priority/p1 On the list but not scheduled team/ce
Projects
None yet
Development

No branches or pull requests

8 participants