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

schedulerName in kube_pod_* metrics group #2207

Closed
PigNatovsky opened this issue Sep 26, 2023 · 1 comment · Fixed by #2222
Closed

schedulerName in kube_pod_* metrics group #2207

PigNatovsky opened this issue Sep 26, 2023 · 1 comment · Fixed by #2222
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@PigNatovsky
Copy link

PigNatovsky commented Sep 26, 2023

What would you like to be added:
It would be great if we will have schedulerName in exported kube_info_metrics.
Why is this needed:
When we have more than one scheduler in the cluster, we need to aggregate some data by scheduler.
Describe the solution you'd like
It could be a metric called kube_pod_scheduler_name with labels set {pod, namespace, uid, schedulerName (or just name)}. Value can be taken from .spec.schedulerName.

@PigNatovsky PigNatovsky added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 26, 2023
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 26, 2023
@dashpole
Copy link
Contributor

dashpole commented Oct 5, 2023

/assign @dgrisonnet
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants