Merge pull request #35523 from windsonsea/hatop

[zh-cn] updated /production-environment/tools/kubeadm/ha-topology.md
This commit is contained in:
Kubernetes Prow Robot 2022-07-28 19:01:11 -07:00 committed by GitHub
commit 54278d7fd2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 10 deletions

View File

@ -44,8 +44,6 @@ kubeadm 静态引导 etcd 集群。
阅读 etcd [集群指南](https://github.com/etcd-io/etcd/blob/release-3.4/Documentation/op-guide/clustering.md#static)以获得更多详细信息。 阅读 etcd [集群指南](https://github.com/etcd-io/etcd/blob/release-3.4/Documentation/op-guide/clustering.md#static)以获得更多详细信息。
{{< /note >}} {{< /note >}}
<!-- body --> <!-- body -->
<!-- <!--
@ -58,16 +56,14 @@ A stacked HA cluster is a [topology](https://en.wikipedia.org/wiki/Network_topol
data storage cluster provided by etcd is stacked on top of the cluster formed by the nodes managed by data storage cluster provided by etcd is stacked on top of the cluster formed by the nodes managed by
kubeadm that run control plane components. kubeadm that run control plane components.
--> -->
堆叠StackedHA 集群是一种这样的[拓扑](https://en.wikipedia.org/wiki/Network_topology) 堆叠StackedHA 集群是一种这样的[拓扑](https://zh.wikipedia.org/wiki/%E7%BD%91%E7%BB%9C%E6%8B%93%E6%89%91)
其中 etcd 分布式数据存储集群堆叠在 kubeadm 管理的控制平面节点上,作为控制平面的一个组件运行。 其中 etcd 分布式数据存储集群堆叠在 kubeadm 管理的控制平面节点上,作为控制平面的一个组件运行。
<!-- <!--
Each control plane node runs an instance of the `kube-apiserver`, `kube-scheduler`, and `kube-controller-manager`. Each control plane node runs an instance of the `kube-apiserver`, `kube-scheduler`, and `kube-controller-manager`.
-->
每个控制平面节点运行 `kube-apiserver`、`kube-scheduler` 和 `kube-controller-manager` 实例。
<!--
The `kube-apiserver` is exposed to worker nodes using a load balancer. The `kube-apiserver` is exposed to worker nodes using a load balancer.
--> -->
每个控制平面节点运行 `kube-apiserver`、`kube-scheduler` 和 `kube-controller-manager` 实例。
`kube-apiserver` 使用负载均衡器暴露给工作节点。 `kube-apiserver` 使用负载均衡器暴露给工作节点。
<!-- <!--
@ -123,7 +119,8 @@ An HA cluster with external etcd is a [topology](https://en.wikipedia.org/wiki/N
<!-- <!--
Like the stacked etcd topology, each control plane node in an external etcd topology runs an instance of the `kube-apiserver`, `kube-scheduler`, and `kube-controller-manager`. And the `kube-apiserver` is exposed to worker nodes using a load balancer. However, etcd members run on separate hosts, and each etcd host communicates with the `kube-apiserver` of each control plane node. Like the stacked etcd topology, each control plane node in an external etcd topology runs an instance of the `kube-apiserver`, `kube-scheduler`, and `kube-controller-manager`. And the `kube-apiserver` is exposed to worker nodes using a load balancer. However, etcd members run on separate hosts, and each etcd host communicates with the `kube-apiserver` of each control plane node.
--> -->
就像堆叠的 etcd 拓扑一样,外部 etcd 拓扑中的每个控制平面节点都运行 `kube-apiserver``kube-scheduler` 和 `kube-controller-manager` 实例。 就像堆叠的 etcd 拓扑一样,外部 etcd 拓扑中的每个控制平面节点都会运行
`kube-apiserver`、`kube-scheduler` 和 `kube-controller-manager` 实例。
同样,`kube-apiserver` 使用负载均衡器暴露给工作节点。但是 etcd 成员在不同的主机上运行, 同样,`kube-apiserver` 使用负载均衡器暴露给工作节点。但是 etcd 成员在不同的主机上运行,
每个 etcd 主机与每个控制平面节点的 `kube-apiserver` 通信。 每个 etcd 主机与每个控制平面节点的 `kube-apiserver` 通信。
@ -137,11 +134,9 @@ the cluster redundancy as much as the stacked HA topology.
<!-- <!--
However, this topology requires twice the number of hosts as the stacked HA topology. However, this topology requires twice the number of hosts as the stacked HA topology.
-->
但此拓扑需要两倍于堆叠 HA 拓扑的主机数量。
<!--
A minimum of three hosts for control plane nodes and three hosts for etcd nodes are required for an HA cluster with this topology. A minimum of three hosts for control plane nodes and three hosts for etcd nodes are required for an HA cluster with this topology.
--> -->
但此拓扑需要两倍于堆叠 HA 拓扑的主机数量。
具有此拓扑的 HA 集群至少需要三个用于控制平面节点的主机和三个用于 etcd 节点的主机。 具有此拓扑的 HA 集群至少需要三个用于控制平面节点的主机和三个用于 etcd 节点的主机。
<!-- <!--