Merge pull request #36415 from my-git9/cni5
[zh-cn] sync content/zh-cn/docs/reference/glossary/cni.md
This commit is contained in:
Kubernetes Prow Robot
GitHub
commit
9fc9bd9e9e
|
|
@ -31,14 +31,11 @@ tags:
|
|||
<!--
|
||||
Container network interface (CNI) plugins are a type of Network plugin that adheres to the appc/CNI specification.
|
||||
-->
|
||||
|
||||
容器网络接口 (CNI) 插件是遵循 appc/CNI 协议的一类网络插件。
|
||||
|
||||
<!--more-->
|
||||
|
||||
<!--
|
||||
* For information on Kubernetes and CNI refer to [this](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
* For information on Kubernetes and CNI, see ["Network plugins"](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
* For information on Kubernetes and CNI, see [**Network plugins**](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni).
|
||||
-->
|
||||
|
||||
* 想了解 Kubernetes 和 CNI 请参考 ["网络插件"](/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni)。
|
||||
* 想了解 Kubernetes 和 CNI 请参考[**网络插件**](/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#cni)。
|
||||
|
|
|
|||
|
|
@ -552,14 +552,14 @@ where `trusted-ca-file`, `cert-file` and `key-file` can be obtained from the des
|
|||
可以从 etcd Pod 的描述中获得 `trusted-ca-file`、`cert-file` 和 `key-file`。
|
||||
|
||||
<!--
|
||||
## Scaling up etcd clusters
|
||||
## Scaling out etcd clusters
|
||||
-->
|
||||
## 为 etcd 集群扩容 {#scaling-up-etcd-clusters}
|
||||
## 为 etcd 集群扩容 {#scaling-out-etcd-clusters}
|
||||
|
||||
<!--
|
||||
Scaling up etcd clusters increases availability by trading off performance.
|
||||
Scaling out etcd clusters increases availability by trading off performance.
|
||||
Scaling does not increase cluster performance nor capability. A general rule
|
||||
is not to scale up or down etcd clusters. Do not configure any auto scaling
|
||||
is not to scale out or in etcd clusters. Do not configure any auto scaling
|
||||
groups for etcd clusters. It is highly recommended to always run a static
|
||||
five-member etcd cluster for production Kubernetes clusters at any officially
|
||||
supported scale.
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ kube-dns in an existing deployment, or by using tools like kubeadm
|
|||
that will deploy and upgrade the cluster for you.
|
||||
-->
|
||||
通过替换现有集群部署中的 kube-dns，或者使用 kubeadm 等工具来为你部署和升级集群，
|
||||
可以在你的集群中使用 CoreDNS 而非 kube-dns，
|
||||
可以在你的集群中使用 CoreDNS 而非 kube-dns。
|
||||
|
||||
<!--
|
||||
## Installing CoreDNS
|
||||
|
|
|
|||
|
|
@ -182,9 +182,9 @@ using the [cpuset cgroup controller](https://www.kernel.org/doc/Documentation/cg
|
|||
-->
|
||||
### static 策略
|
||||
|
||||
`static` 策略针对具有整数型 CPU `requests` 的 `Guaranteed` Pod ，它允许该类 Pod
|
||||
中的容器访问节点上的独占 CPU 资源。这种独占性是使用
|
||||
[cpuset cgroup 控制器](https://www.kernel.org/doc/Documentation/cgroup-v1/cpusets.txt) 来实现的。
|
||||
`static` 策略针对具有整数型 CPU `requests` 的 `Guaranteed` Pod，
|
||||
它允许该类 Pod 中的容器访问节点上的独占 CPU 资源。这种独占性是使用
|
||||
[cpuset cgroup 控制器](https://www.kernel.org/doc/Documentation/cgroup-v1/cpusets.txt)来实现的。
|
||||
|
||||
<!--
|
||||
System services such as the container runtime and the kubelet itself can continue to run on these exclusive CPUs. The exclusivity only extends to other pods.
|
||||
|
|
@ -200,7 +200,7 @@ the node must be drained and CPU manager manually reset by deleting the
|
|||
state file `cpu_manager_state` in the kubelet root directory.
|
||||
-->
|
||||
{{< note >}}
|
||||
CPU 管理器不支持运行时下线和上线 CPUs。此外，如果节点上的在线 CPUs 集合发生变化，
|
||||
CPU 管理器不支持运行时下线和上线 CPU。此外，如果节点上的在线 CPU 集合发生变化，
|
||||
则必须驱逐节点上的 Pod，并通过删除 kubelet 根目录中的状态文件 `cpu_manager_state`
|
||||
来手动重置 CPU 管理器。
|
||||
{{< /note >}}
|
||||
|
|
|
|||
Loading…
Reference in New Issue