-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
kube_pod_resource_request metric is now stable #47471
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @ringerc! |
There's no longer any need to specify the --show-hidden-metrics-for-version option to the scheduler to see the kube_pod_resource_request metric, it in the stable set now. Also mention that authorization must be for /metrics/resources. Simply having /metrics is not enough.
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @ringerc |
To check EasyCLA /easycla |
Thanks @Shubham82 . I'm trying to find out who in my org can approve it. What a painful process for a small docs PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/easycla
@ringerc please sign the CLA |
@reylejano I'm trying, I'm trying. Lots of other things being juggled. |
CLA should be signed soon. |
I've been unable to get the signed CLA accepted, and will raise a support ticket. |
/easycla |
CLA issues resolved. The org had 2 separate orgs registered with the CLA, and only one was working. Rather confusing. Signed. |
Description
The kube scheduler metrics docs at https://kubernetes.io/docs/concepts/cluster-administration/system-metrics/#kube-scheduler-metrics incorrectly stated that the metrics
kube_pod_resource_request
andkube_pod_resource_limit
are only available when passing the scheduler argument--show-hidden-metrics-for-version=1.20
.This argument is not permitted on newer k8s with this value (it must be the same or one lower version than the running k8s), and it's unnecessary since these metrics are in the stable set now anyway: https://kubernetes.io/docs/reference/instrumentation/metrics/
Issue
nil