Skip to content

Commit 5105718

Browse files
author
Tim Bannister
committed
Reinstate PodAndContainerStatsFromCRI docs
Previous changes lost this documentation; reinstate something similar.
1 parent e09bd95 commit 5105718

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

content/en/docs/tasks/debug/debug-cluster/resource-metrics-pipeline.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -270,6 +270,17 @@ Beginning with `metrics-server` 0.6.x, `metrics-server` queries the `/metrics/re
270270
kubelet endpoint, and not `/stats/summary`.
271271
{{< /note >}}
272272

273+
### Summary metrics API source {#summary-api-source}
273274

274275
By default, Kubernetes fetches node summary metrics data using an embedded
275276
[cAdvisor](https://github.com/google/cadvisor) that runs with in the kubelet.
277+
278+
### Summary API data via CRI {#pod-and-container-stats-from-cri}
279+
280+
{{< feature-state for_k8s_version="v1.23" state="alpha" >}}
281+
282+
If you enable the `PodAndContainerStatsFromCRI`
283+
[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) in your
284+
cluster, and you use a container runtime that supports statistics access via
285+
{{< glossary_tooltip term_id="cri" text="Container Runtime Interface">}} (CRI), then
286+
the kubelet fetches Pod- and container-level metric data using CRI, and not via cadvisor.

0 commit comments

Comments
 (0)