kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[zh]Sync kubeadm-10

pull/33663/head
wei.wang 2022-05-14 18:39:43 +08:00
parent bf46c15bdf
commit 2fafe815e2
8 changed files with 131 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-ca.md
View File

@ -85,6 +85,3 @@ kubeadm init phase certs etcd-ca [flags]
</tbody>
</table>

3
content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_all.md
View File

@ -116,6 +116,3 @@ kubeadm init phase kubeconfig all [flags]
</tbody>
</table>

3
content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_all.md
View File

@ -95,6 +95,3 @@ kubeadm join phase control-plane-join all [flags]
</tbody>
</table>

3
content/en/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase_cleanup-node.md
View File

@ -74,6 +74,3 @@ kubeadm reset phase cleanup-node [flags]
</tbody>
</table>

30
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-ca.md
View File

@ -1,3 +1,18 @@
<!--
The file is auto-generated from the Go source code of the component using a generic
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
<!--
Generate the self-signed CA to provision identities for etcd
-->
生成用于为 etcd 设置身份的自签名 CA
<!--
### Synopsis
@ -6,10 +21,10 @@
### 概要
<!--
Generate the self-signed CA to provision identities for etcd, and save them into etcd/ca.cert and etcd/ca.key files.
Generate the self-signed CA to provision identities for etcd, and save them into etcd/ca.crt and etcd/ca.key files.
-->
生成用于为 etcd 设置身份的自签名 CA，并将其保存到 etcd/ca.cert 和 etcd/ca.key 文件中。
生成用于为 etcd 设置身份的自签名 CA，并将其保存到 etcd/ca.crt 和 etcd/ca.key 文件中。
<!--
If both files already exist, kubeadm skips the generation step and existing files will be used.
@ -53,7 +68,9 @@ kubeadm init phase certs etcd-ca [flags]
<!--
The path where to save and store the certificates.
-->
<p>
证书的存储路径。
</p>
</td>
</tr>
@ -65,7 +82,9 @@ The path where to save and store the certificates.
<!--
Path to a kubeadm configuration file.
-->
<p>
kubeadm 配置文件的路径。
</p>
</td>
</tr>
@ -77,7 +96,9 @@ kubeadm 配置文件的路径。
<!--
help for etcd-ca
-->
<p>
etcd-ca 操作的帮助命令
</p>
</td>
</tr>
@ -94,7 +115,9 @@ etcd-ca 操作的帮助命令
<!--
Choose a specific Kubernetes version for the control plane.
-->
<p>
为控制平面选择特定的 Kubernetes 版本。
</p>
</td>
</tr>
@ -122,10 +145,11 @@ Choose a specific Kubernetes version for the control plane.
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<p>
[实验] 到 '真实' 主机根文件系统的路径。
</p>
</td>
</tr>
</tbody>
</table>

38
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_all.md
View File

@ -1,3 +1,18 @@
<!--
The file is auto-generated from the Go source code of the component using a generic
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
<!--
Generate all kubeconfig files
-->
生成所有 kubeconfig 文件
<!--
### Synopsis
@ -8,7 +23,6 @@
<!--
Generate all kubeconfig files
-->
生成所有 kubeconfig 文件
```
@ -36,7 +50,9 @@ kubeadm init phase kubeconfig all [flags]
<!--
The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-->
<p>
API 服务器所公布的其正在监听的 IP 地址。如果没有设置，将使用默认的网络接口。
</p>
</td>
</tr>
@ -53,7 +69,9 @@ API 服务器所公布的其正在监听的 IP 地址。如果没有设置，将
<!--
Port for the API Server to bind to.
-->
<p>
要绑定到 API 服务器的端口。
</p>
</td>
</tr>
@ -70,7 +88,9 @@ Port for the API Server to bind to.
<!--
The path where to save and store the certificates.
-->
<p>
保存和存储证书的路径。
</p>
</td>
</tr>
@ -82,7 +102,9 @@ The path where to save and store the certificates.
<!--
Path to kubeadm configuration file.
-->
<p>
kubeadm 配置文件的路径。
</p>
</td>
</tr>
@ -94,7 +116,9 @@ kubeadm 配置文件的路径。
<!--
Specify a stable IP address or DNS name for the control plane.
-->
<p>
为控制平面指定一个稳定的 IP 地址或 DNS 名称。
</p>
</td>
</tr>
@ -106,7 +130,9 @@ Specify a stable IP address or DNS name for the control plane.
<!--
help for all
-->
<p>
all 操作的帮助命令
</p>
</td>
</tr>
@ -123,7 +149,9 @@ all 操作的帮助命令
<!--
The path where to save the kubeconfig file.
-->
<p>
kubeconfig 文件的保存路径。
</p>
</td>
</tr>
@ -140,7 +168,9 @@ kubeconfig 文件的保存路径。
<!--
Choose a specific Kubernetes version for the control plane.
-->
<p>
为控制平面指定特定的 Kubernetes 版本。
</p>
</td>
</tr>
@ -152,7 +182,9 @@ Choose a specific Kubernetes version for the control plane.
<!--
Specify the node name.
-->
<p>
指定节点名称。
</p>
</td>
</tr>
@ -162,7 +194,6 @@ Specify the node name.
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@ -180,10 +211,11 @@ Specify the node name.
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<p>
[实验] 到 '真实' 主机根文件系统的路径。
</p>
</td>
</tr>
</tbody>
</table>

51
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_all.md
View File

@ -1,3 +1,18 @@
<!--
The file is auto-generated from the Go source code of the component using a generic
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
<!--
Join a machine as a control plane instance
-->
添加作为控制平面实例的机器
<!--
### Synopsis
@ -6,9 +21,8 @@
### 概要
<!--
Joins a machine as a control plane instance
Join a machine as a control plane instance
-->
添加作为控制平面实例的机器
```
@ -18,7 +32,6 @@ kubeadm join phase control-plane-join all [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@ -36,7 +49,9 @@ kubeadm join phase control-plane-join all [flags]
<!--
If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
-->
<p>
如果该节点托管一个新的控制平面实例，则 API 服务器将公布其正在侦听的 IP 地址。如果未设置，则使用默认网络接口。
</p>
</td>
</tr>
@ -48,19 +63,23 @@ If the node should host a new control plane instance, the IP address the API Ser
<!--
Path to kubeadm config file.
-->
<p>
kubeadm 配置文件的路径。
</p>
</td>
</tr>
<tr>
<td colspan="2">--experimental-control-plane</td>
<td colspan="2">--control-plane</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Create a new control plane instance on this node
-->
<p>
在此节点上创建一个新的控制平面实例
</p>
</td>
</tr>
@ -72,7 +91,9 @@ Create a new control plane instance on this node
<!--
help for all
-->
<p>
all 操作的帮助命令
</p>
</td>
</tr>
@ -84,10 +105,29 @@ all 操作的帮助命令
<!--
Specify the node name.
-->
<p>
指定节点名称。
</p>
</td>
</tr>
<tr>
<td colspan="2">--patches string</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>
<!--
Path to a directory that contains files named &quot;target[suffix][+patchtype].extension&quot;. For example, &quot;kube-apiserver0+merge.yaml&quot; or just &quot;etcd.json&quot;. &quot;target&quot; can be one of &quot;kube-apiserver&quot;, &quot;kube-controller-manager&quot;, &quot;kube-scheduler&quot;, &quot;etcd&quot;. &quot;patchtype&quot; can be one of &quot;strategic&quot;, &quot;merge&quot; or &quot;json&quot; and they match the patch formats supported by kubectl. The default &quot;patchtype&quot; is &quot;strategic&quot;. &quot;extension&quot; must be either &quot;json&quot; or &quot;yaml&quot;. &quot;suffix&quot; is an optional string that can be used to determine which patches are applied first alpha-numerically.
-->
包含名为 “target[suffix][+patchtype].extension” 的文件的目录的路径。
例如，“kube-apiserver0+merge.yaml” 或只是 “etcd.json”。
“target” 可以是 “kube-apiserver”、“kube-controller-manager”、“kube-scheduler”、“etcd” 之一。
“patchtype” 可以是 “strategic”、“merge” 或 “json”，它们匹配 kubectl 支持的补丁格式。
默认的 “patchtype” 是 “strategic”。“extension” 必须是 “json” 或 “yaml”。
“suffix” 是一个可选字符串，可用于基于字母数字顺序确定首先应用哪些补丁。
</p></td>
</tr>
</tbody>
</table>
@ -112,10 +152,11 @@ Specify the node name.
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<p>
[实验] 到 '真实' 主机根文件系统的路径。
</p>
</td>
</tr>
</tbody>
</table>

27
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase_cleanup-node.md
View File

@ -1,3 +1,18 @@
<!--
The file is auto-generated from the Go source code of the component using a generic
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
<!--
Run cleanup node.
-->
执行 cleanup node（清理节点）操作。
<!--
### Synopsis
@ -8,7 +23,6 @@
<!--
Run cleanup node.
-->
执行 cleanup node（清理节点）操作。
```
@ -18,7 +32,6 @@ kubeadm reset phase cleanup-node [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@ -41,7 +54,9 @@ kubeadm reset phase cleanup-node [flags]
<!--
The path to the directory where the certificates are stored. If specified, clean this directory.
-->
<p>
存储证书的目录路径。如果已指定，则需要清空此目录。
</p>
</td>
</tr>
@ -53,7 +68,9 @@ The path to the directory where the certificates are stored. If specified, clean
<!--
Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
-->
<p>
要连接的 CRI 套接字的路径。如果为空，则 kubeadm 将尝试自动检测此值；仅当安装了多个CRI 或具有非标准 CRI 插槽时，才使用此选项。
</p>
</td>
</tr>
@ -65,7 +82,9 @@ Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this
<!--
help for cleanup-node
-->
<p>
cleanup-node 操作的帮助命令
</p>
</td>
</tr>
@ -75,7 +94,6 @@ cleanup-node 操作的帮助命令
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@ -93,10 +111,11 @@ cleanup-node 操作的帮助命令
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<p>
[实验] 指向 '真实' 宿主机根文件系统的路径。
</p>
</td>
</tr>
</tbody>
</table>