[zh] Sync concepts pages for architecture and extend-kubernetes

* [zh] Umbrella issue: pages out of sync in concepts section #26177(Misc Batch 4)

```
[x] content/zh/docs/concepts/architecture/controller.md
[x] content/zh/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md
[x] content/zh/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins.md
[x] content/zh/docs/concepts/extend-kubernetes/operator.md
```

* sync with english version in home/_index.md

Signed-off-by: ydFu <ader.ydfu@gmail.com>
pull/26219/head
ydFu 2021-01-24 11:12:39 +08:00
parent a088d1f27a
commit cb4cc0f261
6 changed files with 14 additions and 12 deletions

View File

@ -189,7 +189,7 @@ control loops automatically fix failures. This means that,
potentially, your cluster never reaches a stable state.
As long as the controllers for your cluster are running and able to make
useful changes, it doesn't matter if the overall state is or is not stable.
useful changes, it doesn't matter if the overall state is stable or not.
-->
## 期望状态与当前状态 {#desired-vs-current}

View File

@ -336,10 +336,10 @@ Monitoring agents for device plugin resources can be deployed as a daemon, or as
The canonical directory `/var/lib/kubelet/pod-resources` requires privileged access, so monitoring
agents must run in a privileged security context. If a device monitoring agent is running as a
DaemonSet, `/var/lib/kubelet/pod-resources` must be mounted as a
{{< glossary_tooltip term_id="volume" >}} in the plugin's
{{< glossary_tooltip term_id="volume" >}} in the device monitoring agent's
[PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core).
Support for the "PodResources service" requires `KubeletPodResources` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled. It is enabled by default starting with Kubernetes 1.15.
Support for the "PodResources service" requires `KubeletPodResources` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) to be enabled.
It is enabled by default starting with Kubernetes 1.15 and is v1 since Kubernetes 1.20.
-->
gRPC 服务通过 `/var/lib/kubelet/pod-resources/kubelet.sock` 的 UNIX 套接字来提供服务。
设备插件资源的监控代理程序可以部署为守护进程或者 DaemonSet。
@ -348,11 +348,11 @@ gRPC 服务通过 `/var/lib/kubelet/pod-resources/kubelet.sock` 的 UNIX 套接
如果设备监控代理以 DaemonSet 形式运行,必须要在插件的
[PodSpec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#podspec-v1-core)
中声明将 `/var/lib/kubelet/pod-resources` 目录以
{{< glossary_tooltip text="卷" term_id="volume" >}}的形式被挂载到容器中。
{{< glossary_tooltip text="卷" term_id="volume" >}}的形式被挂载到设备监控代理中。
对“PodResources 服务”的支持要求启用 `KubeletPodResources`
[特性门控](/zh/docs/reference/command-line-tools-reference/feature-gates/)。
从 Kubernetes 1.15 开始默认启用。
从 Kubernetes 1.15 开始默认启用,自从 Kubernetes 1.20开始为 v1
<!--
## Device Plugin integration with the Topology Manager

View File

@ -284,7 +284,7 @@ This option is provided to the network-plugin; currently **only kubenet supports
## Usage Summary
* `--network-plugin=cni` specifies that we use the `cni` network plugin with actual CNI plugin binaries located in `--cni-bin-dir` (default `/opt/cni/bin`) and CNI plugin configuration located in `--cni-conf-dir` (default `/etc/cni/net.d`).
* `--network-plugin=kubenet` specifies that we use the `kubenet` network plugin with CNI `bridge` and `host-local` plugins placed in `/opt/cni/bin` or `cni-bin-dir`.
* `--network-plugin=kubenet` specifies that we use the `kubenet` network plugin with CNI `bridge`, `lo` and `host-local` plugins placed in `/opt/cni/bin` or `cni-bin-dir`.
* `--network-plugin-mtu=9001` specifies the MTU to use, currently only used by the `kubenet` network plugin.
-->
## 用法总结
@ -292,7 +292,7 @@ This option is provided to the network-plugin; currently **only kubenet supports
* `--network-plugin=cni` 用来表明我们要使用 `cni` 网络插件,实际的 CNI 插件
可执行文件位于 `--cni-bin-dir`(默认是 `/opt/cni/bin`)下, CNI 插件配置位于
`--cni-conf-dir`(默认是 `/etc/cni/net.d`)下。
* `--network-plugin=kubenet` 用来表明我们要使用 `kubenet` 网络插件CNI `bridge`
* `--network-plugin=kubenet` 用来表明我们要使用 `kubenet` 网络插件CNI `bridge``lo`
`host-local` 插件位于 `/opt/cni/bin``cni-bin-dir` 中。
* `--network-plugin-mtu=9001` 指定了我们使用的 MTU当前仅被 `kubenet` 网络插件使用。

View File

@ -200,6 +200,7 @@ Operator.
You also implement an Operator (that is, a Controller) using any language / runtime
that can act as a [client for the Kubernetes API](/docs/reference/using-api/client-libraries/).
-->
如果生态系统中没可以实现你目标的 Operator你可以自己编写代码。在

View File

@ -34,7 +34,7 @@ overview:
# button: "View Tutorials"
# button_path: "/docs/tutorials"
# - name: setup
# title: "Set up a cluster"
# title: "Set up a K8s cluster"
# description: "Get Kubernetes running based on your resources and needs."
# button: "Set up Kubernetes"
# button_path: "/docs/setup"
@ -59,7 +59,7 @@ overview:
# button: Contribute to the docs
# button_path: /docs/contribute
# - name: release-notes
# title: Release Notes
# title: K8s Release Notes
# description: If you are installing Kubernetes or upgrading to the newest version, refer to the current release notes.
# button: "Download Kubernetes"
# button_path: "/zh/docs/setup/release/notes"
@ -78,7 +78,7 @@ cards:
button: "查看教程"
button_path: "/zh/docs/tutorials"
- name: setup
title: "设置集群"
title: "设置 K8s 集群"
description: "按照你的资源情况和需求运行 Kubernetes。"
button: "设置 Kubernetes"
button_path: "/zh/docs/setup"
@ -103,7 +103,7 @@ cards:
button: 为文档作贡献
button_path: /zh/docs/contribute
- name: release-notes
title: 发布说明
title: K8s 发布说明
description: 如果你正在安装或升级 Kubernetes最好参考最新的发布说明。
button: "下载 Kubernetes"
button_path: "/zh/docs/setup/release/notes"

View File

@ -55,6 +55,7 @@ The kind [Quick Start](https://kind.sigs.k8s.io/docs/user/quick-start/) page
shows you what you need to do to get up and running with `kind`.
<a class="btn btn-primary" href="https://kind.sigs.k8s.io/docs/user/quick-start/" role="button" aria-label="View kind Quick Start Guide">View kind Quick Start Guide</a>
-->
## kind