Skip to content
This repository has been archived by the owner on Mar 22, 2023. It is now read-only.

Commit

Permalink
Merge pull request kubernetes#40172 from asa3311/Reference-files-to-s…
Browse files Browse the repository at this point in the history
…ync-task-8

[zh-cn]Reference files to sync task 8
  • Loading branch information
k8s-ci-robot authored Mar 22, 2023
2 parents 219cf70 + 4b3dc93 commit fbeadc1
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 21 deletions.
7 changes: 5 additions & 2 deletions content/zh-cn/docs/reference/config-api/_index.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
---
title: 配置 API
weight: 65
weight: 130
---

<!---
title: Configuration APIs
weight: 130
-->
27 changes: 8 additions & 19 deletions content/zh-cn/docs/reference/instrumentation/node-metrics.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,31 +66,20 @@ kubelet endpoint, and not `/stats/summary`.
## Summary metrics API source {#summary-api-source}
By default, Kubernetes fetches node summary metrics data using an embedded
[cAdvisor](https://github.com/google/cadvisor) that runs within the kubelet.
## Summary API data via CRI {#pod-and-container-stats-from-cri}
[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
the kubelet [fetches Pod- and container-level metric data using CRI](/docs/reference/instrumentation/cri-pod-container-metrics), and not via cAdvisor.
-->
## 概要指标 API 源 {#summary-api-source}

默认情况下,Kubernetes 使用 kubelet 内运行的嵌入式 [cAdvisor](https://github.com/google/cadvisor)
获取节点概要指标数据。

## 通过 CRI 获得概要 API 数据 {#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.
-->
如果你在自己的集群中启用 `PodAndContainerStatsFromCRI`
获取节点概要指标数据。如果你在自己的集群中启用 `PodAndContainerStatsFromCRI`
[特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)
且你通过{{< glossary_tooltip term_id="cri" text="容器运行时接口">}} (CRI) 使用支持统计访问的容器运行时,
则 kubelet 将使用 CRI 而不是 cAdvisor 来获取 Pod 和容器级别的指标数据

则 kubelet [将使用 CRI 来获取 Pod 和容器级别的指标数据](/zh-cn/docs/reference/instrumentation/cri-pod-container-metrics)
而不是 cAdvisor 来获取。
## {{% heading "whatsnext" %}}

<!--
Expand Down

0 comments on commit fbeadc1

Please sign in to comment.