Reinstate PodAndContainerStatsFromCRI docs
Previous changes lost this documentation; reinstate something similar.pull/37980/head
parent
e09bd95daf
commit
51057189b0
|
@ -270,6 +270,17 @@ Beginning with `metrics-server` 0.6.x, `metrics-server` queries the `/metrics/re
|
||||||
kubelet endpoint, and not `/stats/summary`.
|
kubelet endpoint, and not `/stats/summary`.
|
||||||
{{< /note >}}
|
{{< /note >}}
|
||||||
|
|
||||||
|
### Summary metrics API source {#summary-api-source}
|
||||||
|
|
||||||
By default, Kubernetes fetches node summary metrics data using an embedded
|
By default, Kubernetes fetches node summary metrics data using an embedded
|
||||||
[cAdvisor](https://github.com/google/cadvisor) that runs with in the kubelet.
|
[cAdvisor](https://github.com/google/cadvisor) that runs with in the kubelet.
|
||||||
|
|
||||||
|
### Summary API data via CRI {#pod-and-container-stats-from-cri}
|
||||||
|
|
||||||
|
{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
|
||||||
|
|
||||||
|
If you enable the `PodAndContainerStatsFromCRI`
|
||||||
|
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) in your
|
||||||
|
cluster, and you use a container runtime that supports statistics access via
|
||||||
|
{{< glossary_tooltip term_id="cri" text="Container Runtime Interface">}} (CRI), then
|
||||||
|
the kubelet fetches Pod- and container-level metric data using CRI, and not via cadvisor.
|
||||||
|
|
Loading…
Reference in New Issue