From 5fd04c3495dca14118255e3767446007c5fdb74b Mon Sep 17 00:00:00 2001 From: pranav-pandey0804 Date: Thu, 30 May 2024 10:37:28 +0530 Subject: [PATCH] changed term id from cri to container-runtime-interface --- content/en/docs/reference/instrumentation/node-metrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/reference/instrumentation/node-metrics.md b/content/en/docs/reference/instrumentation/node-metrics.md index 32eab955bd..df264fc844 100644 --- a/content/en/docs/reference/instrumentation/node-metrics.md +++ b/content/en/docs/reference/instrumentation/node-metrics.md @@ -40,7 +40,7 @@ By default, Kubernetes fetches node summary metrics data using an embedded [cAdvisor](https://github.com/google/cadvisor) that runs within the kubelet. 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 +{{< glossary_tooltip term_id="container-runtime-interface" text="Container Runtime Interface">}} (CRI), then the kubelet [fetches Pod- and container-level metric data using CRI](/docs/reference/instrumentation/cri-pod-container-metrics), and not via cAdvisor. ## {{% heading "whatsnext" %}}