Skip to content

Commit b7b75fb

Browse files
my-git9tengqm
andauthored
[zh-cn]sync architecture/_index duration cluster-autoscaling (#48529)
* [zh-cn]sync architecture/_index duration Signed-off-by: xin.li <[email protected]> * Update _index.md * Update _index.md --------- Signed-off-by: xin.li <[email protected]> Co-authored-by: Qiming Teng <[email protected]>
1 parent ee23103 commit b7b75fb

File tree

3 files changed

+78
-24
lines changed

3 files changed

+78
-24
lines changed

content/zh-cn/docs/concepts/architecture/_index.md

Lines changed: 40 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -22,22 +22,48 @@ usually runs multiple nodes, providing fault-tolerance and high availability.
2222
2323
This document outlines the various components you need to have for a complete and working Kubernetes cluster.
2424
-->
25-
Kubernetes 集群由一个控制平面和一组用于运行容器化应用的工作机器组成,这些工作机器称作节点(Node)。
26-
每个集群至少需要一个工作节点来运行 Pod。
25+
Kubernetes 集群由一个控制平面和一组用于运行容器化应用的工作机器组成,
26+
这些工作机器称作节点(Node)。每个集群至少需要一个工作节点来运行 Pod。
2727

2828
工作节点托管着组成应用负载的 Pod。控制平面管理集群中的工作节点和 Pod。
2929
在生产环境中,控制平面通常跨多台计算机运行,而一个集群通常运行多个节点,以提供容错和高可用。
3030

3131
本文概述了构建一个完整且可运行的 Kubernetes 集群所需的各种组件。
3232

3333
<!--
34-
{{< figure src="/images/docs/kubernetes-cluster-architecture.svg" alt="The control plane (kube-apiserver, etcd, kube-controller-manager, kube-scheduler) and several nodes. Each node is running a kubelet and kube-proxy."
35-
title="Kubernetes cluster components"
36-
caption="**Note:** This diagram presents an example reference architecture for a Kubernetes cluster. The actual distribution of components can vary based on specific cluster setups and requirements." class="diagram-large" >}}
34+
{{< figure src="/images/docs/kubernetes-cluster-architecture.svg"
35+
alt="The control plane (kube-apiserver, etcd, kube-controller-manager, kube-scheduler) and several nodes. Each node is running a kubelet and kube-proxy."
36+
caption="Figure 1. Kubernetes cluster components." class="diagram-large" >}}
3737
-->
38-
{{< figure src="/images/docs/kubernetes-cluster-architecture.svg" alt="控制平面(kube-apiserver、etcd、kube-controller-manager、kube-scheduler)和多个节点。每个节点运行 kubelet 和 kube-proxy。"
39-
title="Kubernetes 集群组件"
40-
caption="**注意:** 此图展示了 Kubernetes 集群的参考架构示例。这些组件的实际分布可能会基于特定的集群设置和要求而有所不同。" class="diagram-large" >}}
38+
{{< figure src="/images/docs/kubernetes-cluster-architecture.svg"
39+
alt="控制平面(kube-apiserver、etcd、kube-controller-manager、kube-scheduler)和多个节点。每个节点运行 kubelet 和 kube-proxy。"
40+
caption="图 1. Kubernetes 集群组件。" class="diagram-large" >}}
41+
42+
<!--
43+
{{ /* details summary="About this architecture" */ }}
44+
-->
45+
{{< details summary="关于此架构" >}}
46+
<!--
47+
The diagram in Figure 1 presents an example reference architecture for a Kubernetes cluster.
48+
The actual distribution of components can vary based on specific cluster setups and requirements.
49+
-->
50+
图 1 中的图表展示了 Kubernetes 集群的示例参考架构,
51+
组件的实际分布可能根据特定的集群设置和要求而有所不同。
52+
53+
<!--
54+
In the diagram, each node runs the [`kube-proxy`](#kube-proxy) component. You need a
55+
network proxy component on each node to ensure that the
56+
{{< glossary_tooltip text="Service" term_id="service">}} API and associated behaviors
57+
are available on your cluster network. However, some network plugins provide their own,
58+
third party implementation of proxying. When you use that kind of network plugin,
59+
the node does not need to run `kube-proxy`.
60+
-->
61+
图中每个节点都运行 [`kube-proxy`](#kube-proxy) 组件。
62+
你需要在每个节点上安装一个网络代理组件,以确保 {{< glossary_tooltip text="Service" term_id="service">}}
63+
API 和相关行为在你的集群网络上可用。
64+
但是,一些网络插件为流量代理提供了自己的第三方实现。
65+
当你使用那种网络插件时,节点便不需要运行 `kube-proxy`
66+
{{< /details >}}
4167

4268
<!--
4369
## Control plane components
@@ -50,7 +76,8 @@ as well as detecting and responding to cluster events (for example, starting up
5076
## 控制平面组件 {#control-plane-components}
5177

5278
控制平面组件会为集群做出全局决策,比如资源的调度。
53-
以及检测和响应集群事件,例如当不满足 Deployment 的 `{{< glossary_tooltip text="replicas" term_id="replica" >}}`
79+
以及检测和响应集群事件,例如当不满足 Deployment 的
80+
`{{< glossary_tooltip text="replicas" term_id="replica" >}}`
5481
字段时,要启动新的 {{< glossary_tooltip text="Pod" term_id="pod">}})。
5582

5683
<!--
@@ -134,6 +161,8 @@ The following controllers can have cloud provider dependencies:
134161
- Route 控制器:用于在底层云基础架构中设置路由
135162
- Service 控制器:用于创建、更新和删除云平台上的负载均衡器
136163

164+
---
165+
137166
<!--
138167
## Node components
139168
@@ -332,7 +361,8 @@ balancing factors such as operational complexity, performance, and management ov
332361
-->
333362
### 集群管理工具 {#cluster-management-tools}
334363

335-
像 kubeadm、kops 和 Kubespray 这样的工具提供了不同的集群部署和管理方法,每种方法都有自己的组件布局和管理方式。
364+
像 kubeadm、kops 和 Kubespray 这样的工具提供了不同的集群部署和管理方法,
365+
每种方法都有自己的组件布局和管理方式。
336366

337367
Kubernetes 架构的灵活性使各组织能够根据特定需求调整其集群,平衡操作复杂性、性能和管理开销等因素。
338368

content/zh-cn/docs/concepts/cluster-administration/cluster-autoscaling.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ node capacity (CPU, memory, and other node resources) available in your cluster.
6565
6666
You can use the [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler) to manage the scale of your nodes automatically.
6767
The cluster autoscaler can integrate with a cloud provider, or with Kubernetes'
68-
[cluster API](https://github.com/kubernetes/autoscaler/blob/c6b754c359a8563050933a590f9a5dece823c836/cluster-autoscaler/cloudprovider/clusterapi/README.md),
68+
[cluster API](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/clusterapi/README.md),
6969
to achieve the actual node management that's needed.
7070
-->
7171
## 自动水平扩缩容 {#autoscaling-horizontal}
@@ -74,7 +74,7 @@ to achieve the actual node management that's needed.
7474

7575
你可以使用 [Cluster Autoscaler](https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler)
7676
自动管理节点的数目规模。Cluster Autoscaler 可以与云驱动或 Kubernetes 的
77-
[Cluster API](https://github.com/kubernetes/autoscaler/blob/c6b754c359a8563050933a590f9a5dece823c836/cluster-autoscaler/cloudprovider/clusterapi/README.md)
77+
[Cluster API](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/clusterapi/README.md)
7878
集成,以完成实际所需的节点管理。
7979

8080
<!--
@@ -83,7 +83,7 @@ removes nodes when those nodes are empty.
8383
8484
#### Cloud provider integrations {#cluster-autoscaler-providers}
8585
86-
The [README](https://github.com/kubernetes/autoscaler/tree/c6b754c359a8563050933a590f9a5dece823c836/cluster-autoscaler#readme)
86+
The [README](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/README.md)
8787
for the cluster autoscaler lists some of the cloud provider integrations
8888
that are available.
8989
-->
@@ -93,8 +93,8 @@ that are available.
9393
#### 云驱动集成组件 {#cluster-autoscaler-providers}
9494

9595
Cluster Autoscaler 的
96-
[README](https://github.com/kubernetes/autoscaler/tree/c6b754c359a8563050933a590f9a5dece823c836/cluster-autoscaler#readme)
97-
列举了一些可用的云驱动集成组件
96+
[README](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/README.md)
97+
中列举了一些可用的云驱动集成组件
9898

9999
<!--
100100
## Cost-aware multidimensional scaling {#autoscaling-multi-dimension}
@@ -153,8 +153,12 @@ cloud providers:
153153
-->
154154
在 Karpenter 的核心与以下云驱动之间,存在可用的集成组件:
155155

156+
<!--
156157
- [Amazon Web Services](https://github.com/aws/karpenter-provider-aws)
157158
- [Azure](https://github.com/Azure/karpenter-provider-azure)
159+
-->
160+
- [亚马逊 Web 服务(Amazon Web Service)](https://github.com/aws/karpenter-provider-aws)
161+
- [Azure](https://github.com/Azure/karpenter-provider-azure)
158162

159163
<!--
160164
## Related components
@@ -189,7 +193,7 @@ and cores, and scales the number of replicas of the target workload accordingly.
189193
#### Cluster Proportional Autoscaler
190194

191195
对于需要基于集群大小进行扩缩容的工作负载(例如 `cluster-dns` 或其他系统组件),
192-
你可以使用 [Cluster Proportional Autoscaler](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler)
196+
你可以使用 [**Cluster Proportional Autoscaler**](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler)
193197

194198
Cluster Proportional Autoscaler 监视可调度节点和核心的数量,并相应地调整目标工作负载的副本数量。
195199

content/zh-cn/docs/reference/glossary/duration.md

Lines changed: 28 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,7 @@ id: duration
44
date: 2024-10-05
55
full_link:
66
short_description: >
7-
以字符串形式指定的时间间隔,格式符合 Go 语言的
8-
[time.Duration](https://pkg.go.dev/time),
9-
允许使用秒、分钟和小时等不同单位灵活地指定时间。
7+
表示时间量的字符串值。
108
aka:
119
tags:
1210
- fundamental
@@ -17,15 +15,37 @@ id: duration
1715
date: 2024-10-05
1816
full_link:
1917
short_description: >
20-
A time interval specified as a string in the format accepted by Go's [time.Duration](https://pkg.go.dev/time), allowing for flexible time specifications using various units like seconds, minutes, and hours.
18+
A string value representing an amount of time.
2119
aka:
2220
tags:
2321
- fundamental
2422
-->
2523

2624
<!--
27-
In Kubernetes APIs, a duration must be non-negative and is typically expressed with a suffix.
28-
For example, `5s` for five seconds or `1m30s` for one minute and thirty seconds.
25+
A string value representing an amount of time.
2926
-->
30-
在 Kubernetes API 中,duration 必须是非负的,通常带有后缀单位。
31-
例如,`5s` 表示五秒,`1m30s` 表示一分三十秒。
27+
表示时间量的字符串值。
28+
29+
<!--more-->
30+
31+
<!--
32+
The format of a (Kubernetes) duration is based on the
33+
[`time.Duration`](https://pkg.go.dev/time#Duration) type from the Go programming language.
34+
-->
35+
(Kubernetes 中)持续时间的格式基于 Go 编程语言中的 [`time.Duration`](https://pkg.go.dev/time#Duration) 类型。
36+
37+
<!--
38+
In Kubernetes APIs that use durations, the value is expressed as series of a non-negative
39+
integers combined with a time unit suffix. You can have more than one time quantity and
40+
the duration is the sum of those time quantities.
41+
The valid time units are "ns", "µs" (or "us"), "ms", "s", "m", and "h".
42+
-->
43+
在使用持续时间的 Kubernetes API 中,该值表示为一系列非负整数与时间单位后缀的组合。
44+
你可以设置多个时间量,并且持续时间是这些时间量的总和。
45+
有效的时间单位为 "ns"、"µs"(或 "us")、"ms"、"s"、"m" 和 "h"。
46+
47+
<!--
48+
For example: `5s` represents a duration of five seconds, and `1m30s` represents a duration
49+
of one minute and thirty seconds.
50+
-->
51+
例如:`5s` 代表时长为五秒,`1m30s` 代表时长为一分三十秒。

0 commit comments

Comments
 (0)