Skip to content

Commit 4aa44ee

Browse files
committed
kube_pod_resource_request metric is now stable
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.
1 parent ad6351d commit 4aa44ee

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

content/en/docs/concepts/cluster-administration/system-metrics.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -170,9 +170,12 @@ Once a pod reaches completion (has a `restartPolicy` of `Never` or `OnFailure` a
170170
the series is no longer reported since the scheduler is now free to schedule other pods to run.
171171
The two metrics are called `kube_pod_resource_request` and `kube_pod_resource_limit`.
172172

173-
The metrics are exposed at the HTTP endpoint `/metrics/resources` and require the same
174-
authorization as the `/metrics` endpoint on the scheduler. You must use the
175-
`--show-hidden-metrics-for-version=1.20` flag to expose these alpha stability metrics.
173+
The metrics are exposed at the HTTP endpoint `/metrics/resources`. They require
174+
authorization for the `/metrics/resources` endpoint, usually granted by a
175+
ClusterRole with the `get` verb for the `/metrics/resources` non-resource URL.
176+
177+
On Kubernetes 1.21 you must use the `--show-hidden-metrics-for-version=1.20`
178+
flag to expose these alpha stability metrics.
176179

177180
## Disabling metrics
178181

0 commit comments

Comments
 (0)