whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[zh] Fix table format for kubeadm commands

Browse Source
This commit is contained in:
Qiming Teng
2020-05-27 17:37:34 +08:00
parent 1a87ff928e
commit b719fccc1d
108 changed files with 10196 additions and 10188 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm.md
+10 -2
View File
@@ -2,10 +2,9 @@
<!--
### Synopsis
-->
### 摘要
<!--
┌──────────────────────────────────────────────────────────┐
│ KUBEADM │
@@ -15,6 +14,8 @@
│ https://github.com/kubernetes/kubeadm/issues │
└──────────────────────────────────────────────────────────┘
-->
```
┌──────────────────────────────────────────────────────────┐
│ KUBEADM │
│ 轻松创建一个安全的 Kubernetes 集群 │
@@ -22,10 +23,12 @@
│ 给我们反馈意见的地址： │
│ https://github.com/kubernetes/kubeadm/issues │
└──────────────────────────────────────────────────────────┘
```
<!--
Example usage:
-->
用途示例：
<!--
@@ -33,6 +36,7 @@ Example usage:
(which controls the cluster), and one worker node
(where your workloads, like Pods and Deployments run).
-->
创建一个有两台机器的集群，包含一个主节点（用来控制集群），和一个工作节点（运行您的工作负载，像 Pod 和 Deployment）。
<!--
@@ -50,6 +54,8 @@ Example usage:
You can then repeat the second step on as many other machines as you like.
-->
```
┌──────────────────────────────────────────────────────────┐
│ 在第一台机器上： │
├──────────────────────────────────────────────────────────┤
@@ -61,12 +67,14 @@ Example usage:
├──────────────────────────────────────────────────────────┤
│ worker# kubeadm join &lt;arguments-returned-from-init&gt;│
└──────────────────────────────────────────────────────────┘
```
您可以重复第二步，向集群添加更多机器。
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha.md
+4 -3
View File
@@ -2,17 +2,19 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Kubeadm experimental sub-commands
-->
kubeadm 实验子命令
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -37,11 +39,10 @@ kubeadm 实验子命令
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_certificate-key.md
+7 -7
View File
@@ -2,21 +2,21 @@
<!--
### Synopsis
-->
### 概要
<!--
This command will print out a secure randomly-generated certificate key that can be used with
the "init" command.
-->
该命令将打印出可以与 “init” 命令一起使用的安全随机生成的证书密钥。
该命令将打印出可以与 "init" 命令一起使用的安全的随机生成的证书密钥。
<!--
You can also use "kubeadm init --upload-certs" without specifying a certificate key and it will generate and print one for you.
You can also use "kubeadm init -upload-certs" without specifying a certificate key and it will generate and print one for you.
-->
您也可以使用 “kubeadm init --upload-certs” 而无需指定证书密钥，它将为您生成并打印一个证书密钥。
您也可以使用 `kubeadm init --upload-certs` 而无需指定证书密钥，它将为您生成并打印一个证书密钥。
```
kubeadm alpha certs certificate-key [flags]
@@ -25,6 +25,7 @@ kubeadm alpha certs certificate-key [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -49,11 +50,10 @@ kubeadm alpha certs certificate-key [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_check-expiration.md
+5 -14
View File
@@ -7,6 +7,7 @@
<!--
Checks expiration for the certificates in the local PKI managed by kubeadm.
-->
检查 kubeadm 管理的本地 PKI 中证书的到期时间。
```
@@ -43,9 +44,7 @@ kubeadm alpha certs check-expiration [flags]
<td colspan="2">--config string</td>
</tr>
<tr>
<!--
<td></td><td style="line-height: 130%; word-wrap: break-word;">Path to a kubeadm configuration file.</td>
-->
<!-- td></td><td style="line-height: 130%; word-wrap: break-word;">Path to a kubeadm configuration file.</td -->
<td></td><td style="line-height: 130%; word-wrap: break-word;">kubeadm 配置文件的路径</td>
</tr>
@@ -53,20 +52,14 @@ kubeadm alpha certs check-expiration [flags]
<td colspan="2">-h, --help</td>
</tr>
<tr>
<!--
<td></td><td style="line-height: 130%; word-wrap: break-word;">help for check-expiration</td>
-->
<!-- td></td><td style="line-height: 130%; word-wrap: break-word;">help for check-expiration</td -->
<td></td><td style="line-height: 130%; word-wrap: break-word;">check-expiration 的帮助命令</td>
</tr>
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
<!-- ### Options inherited from parent commands -->
### 继承于父命令的选项
@@ -81,9 +74,7 @@ kubeadm alpha certs check-expiration [flags]
<td colspan="2">--rootfs string</td>
</tr>
<tr>
<!--
<td></td><td style="line-height: 130%; word-wrap: break-word;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-->
<!-- td></td><td style="line-height: 130%; word-wrap: break-word;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td -->
<td></td><td style="line-height: 130%; word-wrap: break-word;">[实验] 到'真实'主机根文件系统的路径。</td>
</tr>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用子命令列表。
```
@@ -17,6 +18,7 @@ kubeadm alpha certs renew [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -41,11 +43,10 @@ kubeadm alpha certs renew [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_admin.conf.md
+14 -19
View File
@@ -2,27 +2,32 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate embedded in the kubeconfig file for the admin to use and for kubeadm itself.
-->
续订 kubeconfig 文件中嵌入的证书，供管理员 和 kubeadm 自身使用。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
无论证书的到期日期如何，续订都是无条件进行的；SAN 等额外属性将基于现有文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订会尝试使用由 kubeadm 管理的本地 PKI 中的证书机构；作为替代方案，也可以使用 K8s certificate API 进行证书续订，或者（作为最后一种选择）生成 CSR 请求。
默认情况下，续订会尝试使用由 kubeadm 管理的本地 PKI 中的证书机构；作为替代方案，
也可以使用 K8s certificate API 进行证书续订，或者（作为最后一种选择）生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防证书文件在其他地方使用。
```
@@ -32,6 +37,7 @@ kubeadm alpha certs renew admin.conf [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -43,9 +49,7 @@ kubeadm alpha certs renew admin.conf [flags]
<tr>
<td colspan="2">
<!--
--cert-dir string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/pki"
-->
<!-- --cert-dir string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/pki" -->
--cert-dir string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值："/etc/kubernetes/pki"
</td>
</tr>
@@ -63,9 +67,7 @@ kubeadm alpha certs renew admin.conf [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Path to a kubeadm configuration file.
-->
<!-- Path to a kubeadm configuration file. -->
kubeadm 配置文件的路径。
</td>
</tr>
@@ -75,9 +77,7 @@ kubeadm alpha certs renew admin.conf [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path to output the CSRs and private keys to
-->
<!-- The path to output the CSRs and private keys to -->
CSR 和私钥的输出路径
</td>
</tr>
@@ -99,9 +99,7 @@ kubeadm alpha certs renew admin.conf [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for admin.conf
-->
<!-- help for admin.conf -->
admin.conf 操作的帮助命令
</td>
</tr>
@@ -111,9 +109,7 @@ kubeadm alpha certs renew admin.conf [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.
-->
<!-- The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. -->
与集群通信时使用的 kubeconfig 文件。如果未设置该参数，则可以在一组标准位置中搜索现有的 kubeconfig 文件。
</td>
</tr>
@@ -133,11 +129,10 @@ kubeadm alpha certs renew admin.conf [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_all.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew all known certificates necessary to run the control plane. Renewals are run unconditionally, regardless of expiration date. Renewals can also be run individually for more control.
-->
续订运行控制平面所需的所有已知证书。续订是无条件进行的，与到期日期无关。续订也可以单独运行以进行更多控制。
```
@@ -17,6 +18,7 @@ kubeadm alpha certs renew all [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -123,11 +125,10 @@ kubeadm alpha certs renew all [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_apiserver-etcd-client.md
+17 -26
View File
@@ -2,27 +2,32 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate the apiserver uses to access etcd.
-->
续订 apiserver 用于访问 etcd 的证书。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
无论证书的到期日期如何，续订都会无条件地进行；SAN 等额外属性将基于现有文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订尝试在 kubeadm 管理的本地 PKI 中使用证书颁发机构；作为替代方案，可以使用 K8s 证书 API 进行证书更新，或者作为最后一个选择来生成 CSR 请求。
默认情况下，续订尝试在 kubeadm 管理的本地 PKI 中使用证书颁发机构；作为替代方案，
可以使用 K8s 证书 API 进行证书更新，或者作为最后一个选择来生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防文件在其他地方使用。
```
@@ -32,6 +37,7 @@ kubeadm alpha certs renew apiserver-etcd-client [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -43,17 +49,13 @@ kubeadm alpha certs renew apiserver-etcd-client [flags]
<tr>
<td colspan="2">
<!--
--cert-dir string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/pki"
-->
<!-- cert-dir string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/pki" -->
--cert-dir string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值："/etc/kubernetes/pki"
</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path where to save and store the certificates.
-->
<!-- The path where to save and store the certificates. -->
存储证书的路径。
</td>
</tr>
@@ -63,9 +65,7 @@ kubeadm alpha certs renew apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Path to a kubeadm configuration file.
-->
<!-- Path to a kubeadm configuration file. -->
kubeadm 配置文件的路径。
</td>
</tr>
@@ -75,9 +75,7 @@ kubeadm alpha certs renew apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path to output the CSRs and private keys to
-->
<!-- The path to output the CSRs and private keys to -->
输出 CSR 和私钥的路径
</td>
</tr>
@@ -87,9 +85,7 @@ kubeadm alpha certs renew apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Create CSRs instead of generating certificates
-->
<!-- Create CSRs instead of generating certificates -->
创建 CSR 而不是生成证书
</td>
</tr>
@@ -99,9 +95,7 @@ kubeadm alpha certs renew apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for apiserver-etcd-client
-->
<!-- help for apiserver-etcd-client -->
apiserver-etcd-client 操作的帮助命令
</td>
</tr>
@@ -128,9 +122,7 @@ kubeadm alpha certs renew apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Use the Kubernetes certificate API to renew certificates
-->
<!-- Use the Kubernetes certificate API to renew certificates -->
使用 Kubernetes 证书 API 续订证书
</td>
</tr>
@@ -143,6 +135,7 @@ kubeadm alpha certs renew apiserver-etcd-client [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -157,9 +150,7 @@ kubeadm alpha certs renew apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 到 '真实' 主机根文件系统的路径。
</td>
</tr>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_apiserver-kubelet-client.md
+9 -4
View File
@@ -2,27 +2,32 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate for the API server to connect to kubelet.
-->
续订 apiserver 用于连接 kubelet 的证书。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
无论证书的到期日期如何，续订都会无条件地进行；SAN 等额外属性将基于现有文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订尝试使用位于 kubeadm 所管理的本地 PKI 中的证书颁发机构；作为替代方案，也可能调用 K8s 证书 API 进行证书更新；亦或者，作为最后一个选择，生成 CSR 请求。
默认情况下，续订尝试使用位于 kubeadm 所管理的本地 PKI 中的证书颁发机构；作为替代方案，
也可能调用 K8s 证书 API 进行证书更新；亦或者，作为最后一个选择，生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防文件在其他地方使用。
```
@@ -32,6 +37,7 @@ kubeadm alpha certs renew apiserver-kubelet-client [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -138,11 +144,10 @@ kubeadm alpha certs renew apiserver-kubelet-client [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_apiserver.md
+9 -4
View File
@@ -2,27 +2,32 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate for serving the Kubernetes API.
-->
续订用于提供 Kubernetes API 的证书。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
无论证书的到期日期如何，续订都会无条件地进行；SAN 等额外属性将基于现有文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订尝试在 kubeadm 管理的本地 PKI 中使用证书颁发机构；作为替代方案，可以使用 K8s 证书 API 进行证书更新，或者作为最后一个选择来生成 CSR 请求。
默认情况下，续订尝试在 kubeadm 管理的本地 PKI 中使用证书颁发机构；作为替代方案，
可以使用 K8s 证书 API 进行证书更新，或者作为最后一个选择来生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防文件在其他地方使用。
```
@@ -32,6 +37,7 @@ kubeadm alpha certs renew apiserver [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -138,11 +144,10 @@ kubeadm alpha certs renew apiserver [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_controller-manager.conf.md
+9 -4
View File
@@ -2,27 +2,32 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate embedded in the kubeconfig file for the controller manager to use.
-->
续订 kubeconfig 文件中嵌入的证书，以供控制器管理器（controller manager）使用。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
续订无条件地进行，与证书的到期日期无关；SAN 等额外属性将基于现有的文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订会尝试在 kubeadm 管理的本地 PKI 中使用证书颁发机构；作为替代方案，可以使用 K8s 证书 API 进行证书续订；亦或者，作为最后一种选择，生成 CSR 请求。
默认情况下，续订会尝试在 kubeadm 管理的本地 PKI 中使用证书颁发机构；作为替代方案，
可以使用 K8s 证书 API 进行证书续订；亦或者，作为最后一种选择，生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防文件在其他地方使用。
```
@@ -32,6 +37,7 @@ kubeadm alpha certs renew controller-manager.conf [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -138,11 +144,10 @@ kubeadm alpha certs renew controller-manager.conf [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_etcd-healthcheck-client.md
+7 -6
View File
@@ -2,27 +2,31 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate for liveness probes to healthcheck etcd.
-->
续订 etcd 健康检查的活跃性探针的证书。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
无论证书的到期日期如何，续订都是无条件进行的；SAN 等额外属性将基于现有文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订会尝试使用由 kubeadm 管理的本地 PKI 中的证书机构；作为替代方案，也可以使用 K8s certificate API 进行证书续订，或者（作为最后一种选择）生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防证书文件在其他地方使用。
```
@@ -32,6 +36,7 @@ kubeadm alpha certs renew etcd-healthcheck-client [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -138,11 +143,10 @@ kubeadm alpha certs renew etcd-healthcheck-client [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -167,6 +171,3 @@ kubeadm alpha certs renew etcd-healthcheck-client [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_etcd-peer.md
+7 -6
View File
@@ -2,27 +2,31 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate for etcd nodes to communicate with each other.
-->
续订 etcd 节点间用来相互通信的证书。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
无论证书的到期日期如何，续订都是无条件进行的；SAN 等额外属性将基于现有文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订会尝试使用由 kubeadm 管理的本地 PKI 中的证书机构；作为替代方案，也可以使用 K8s certificate API 进行证书续订，或者（作为最后一种选择）生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防证书文件在其他地方使用。
```
@@ -32,6 +36,7 @@ kubeadm alpha certs renew etcd-peer [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -138,11 +143,10 @@ kubeadm alpha certs renew etcd-peer [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -167,6 +171,3 @@ kubeadm alpha certs renew etcd-peer [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_etcd-server.md
+7 -6
View File
@@ -2,27 +2,31 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate for serving etcd.
-->
续订用于提供 etcd 的证书。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
续订无条件地进行，与证书的到期日期无关；SAN 等额外属性将基于现有的文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订会尝试在 kubeadm 管理的本地 PKI 中使用证书颁发机构；作为替代方案，可以使用 K8s 证书 API 进行证书续订，或者作为最后一种选择来生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防文件在其他地方使用。
```
@@ -32,6 +36,7 @@ kubeadm alpha certs renew etcd-server [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -138,11 +143,10 @@ kubeadm alpha certs renew etcd-server [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -167,6 +171,3 @@ kubeadm alpha certs renew etcd-server [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_front-proxy-client.md
+8 -6
View File
@@ -2,27 +2,31 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate for the front proxy client.
-->
为前端代理客户端续订证书。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
无论证书的到期日期如何，续订都会无条件地进行；SAN 等额外属性将基于现有文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订尝试使用位于 kubeadm 所管理的本地 PKI 中的证书颁发机构；作为替代方案，也可能使用 K8s 证书 API 进行证书续订；亦或者，作为最后一种方案，生成 CSR 请求。
默认情况下，续订尝试使用位于 kubeadm 所管理的本地 PKI 中的证书颁发机构；作为替代方案，
也可以使用 K8s 证书 API 进行证书续订；亦或者，作为最后一种方案，生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防文件在其他地方使用。
```
@@ -32,6 +36,7 @@ kubeadm alpha certs renew front-proxy-client [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -135,11 +140,10 @@ kubeadm alpha certs renew front-proxy-client [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -164,5 +168,3 @@ kubeadm alpha certs renew front-proxy-client [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_certs_renew_scheduler.conf.md
+7 -6
View File
@@ -2,27 +2,31 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Renew the certificate embedded in the kubeconfig file for the scheduler manager to use.
-->
续订 kubeconfig 文件中嵌入的证书，以供调度管理器使用。
<!--
Renewals run unconditionally, regardless of certificate expiration date; extra attributes such as SANs will be based on the existing file/certificates, there is no need to resupply them.
-->
续订无条件地进行，与证书的到期日期无关；SAN 等额外属性将基于现有的文件/证书，因此无需重新提供它们。
<!--
Renewal by default tries to use the certificate authority in the local PKI managed by kubeadm; as alternative it is possible to use K8s certificate API for certificate renewal, or as a last option, to generate a CSR request.
-->
默认情况下，续订会尝试在 kubeadm 管理的本地 PKI 中使用证书颁发机构；作为替代方案，可以使用 K8s 证书 API 进行证书续订；亦或者，作为最后一种选择，生成 CSR 请求。
<!--
After renewal, in order to make changes effective, is is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防文件在其他地方使用。
```
@@ -32,6 +36,7 @@ kubeadm alpha certs renew scheduler.conf [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -138,11 +143,10 @@ kubeadm alpha certs renew scheduler.conf [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -167,6 +171,3 @@ kubeadm alpha certs renew scheduler.conf [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubeconfig.md
+7 -15
View File
@@ -2,22 +2,23 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Kubeconfig file utilities.
-->
kubeconfig 文件应用程序。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
<!-- Alpha Disclaimer: this command is currently alpha. -->
Alpha 免责声明：此命令当前为 alpha 功能。
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -32,9 +33,7 @@ Alpha 免责声明：此命令当前为 alpha 功能。
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for kubeconfig
-->
<!-- help for kubeconfig -->
kubeconfig 操作的帮助命令
</td>
</tr>
@@ -42,11 +41,8 @@ Alpha 免责声明：此命令当前为 alpha 功能。
</tbody>
</table>
<!-- ### Options inherited from parent commands -->
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -72,7 +68,3 @@ Alpha 免责声明：此命令当前为 alpha 功能。
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubeconfig_user.md
+6 -7
View File
@@ -2,17 +2,19 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Output a kubeconfig file for an additional user.
-->
为其他用户输出 kubeconfig 文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 Alpha 功能。
```
@@ -22,6 +24,7 @@ kubeadm alpha kubeconfig user [flags]
<!--
### Examples # Output a kubeconfig file for an additional user named foo
-->
### 示例
```
@@ -32,6 +35,7 @@ kubeadm alpha kubeconfig user [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -138,11 +142,10 @@ kubeadm alpha kubeconfig user [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -167,7 +170,3 @@ kubeadm alpha kubeconfig user [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet.md
+4 -6
View File
@@ -2,17 +2,19 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用子命令列表。
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -37,11 +39,10 @@ This command is not meant to be run on its own. See list of available subcommand
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -66,6 +67,3 @@ This command is not meant to be run on its own. See list of available subcommand
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet_config.md
+5 -9
View File
@@ -2,17 +2,19 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用子命令列表。
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -27,9 +29,7 @@ This command is not meant to be run on its own. See list of available subcommand
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for config
-->
<!-- help for config -->
config 操作的帮助命令
</td>
</tr>
@@ -37,11 +37,10 @@ This command is not meant to be run on its own. See list of available subcommand
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -66,6 +65,3 @@ This command is not meant to be run on its own. See list of available subcommand
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet_config_download.md
+13 -15
View File
@@ -2,19 +2,21 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Download the kubelet configuration from a ConfigMap of the form "kubelet-config-1.X" in the cluster, where X is the minor version of the kubelet. Either kubeadm autodetects the kubelet version by exec-ing "kubelet --version" or respects the --kubelet-version parameter.
-->
从集群中形式为 "kubelet-config-1.X" 的 ConfigMap 中下载 kubelet 配置，其中 X 是 kubelet 的次要版本。kubeadm 要么通过执行 "kubelet --version" 自动检测 kubelet 版本，要么传递 --kubelet-version 参数。
从集群中形式为 "kubelet-config-1.X" 的 ConfigMap 中下载 kubelet 配置，其中 X 是 kubelet 的次要版本。
kubeadm 要么通过执行 "kubelet --version" 自动检测 kubelet 版本，要么传递 --kubelet-version 参数。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 Alpha 功能。
Alpha 免责声明：此命令当前为 Alpha 功能。
```
kubeadm alpha kubelet config download [flags]
@@ -23,28 +25,29 @@ kubeadm alpha kubelet config download [flags]
<!--
### Examples
-->
### 示例
<!--
```
# Download the kubelet configuration from the ConfigMap in the cluster. Autodetect the kubelet version.
kubeadm alpha phase kubelet config download
# Download the kubelet configuration from the ConfigMap in the cluster. Use a specific desired kubelet version.
kubeadm alpha phase kubelet config download --kubelet-version 1.16.0
```
kubeadm alpha phase kubelet config download kubelet-version 1.16.0
-->
```
# 从集群中的 ConfigMap 下载 kubelet 配置。自动检测 kubelet 版本。
下载 kubeadm alpha phase kubelet 配置
kubeadm alpha phase kubelet config download
# 从集群中的 ConfigMap 下载 kubelet 配置。使用特定的所需 kubelet 版本。
kubeadm alpha phase kubelet 配置下载 --kubelet-version 1.16.0
kubeadm alpha phase kubelet config download --kubelet-version 1.16.0
```
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -88,9 +91,7 @@ kubeadm alpha kubelet config download [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The desired version for the kubelet. Defaults to being autodetected from 'kubelet --version'.
-->
<!-- The desired version for the kubelet. Defaults to being autodetected from 'kubelet -version'. -->
kubelet 所需版本。默认为从 'kubelet --version' 中自动检测到。
</td>
</tr>
@@ -98,11 +99,10 @@ kubeadm alpha kubelet config download [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -127,5 +127,3 @@ kubeadm alpha kubelet config download [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_kubelet_config_enable-dynamic.md
+1 -2
View File
@@ -105,11 +105,10 @@ kubeadm alpha kubelet config enable-dynamic [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_selfhosting.md
+4 -3
View File
@@ -2,17 +2,19 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用子命令列表。
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -37,11 +39,10 @@ This command is not meant to be run on its own. See list of available subcommand
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_alpha_selfhosting_pivot.md
+7 -3
View File
@@ -2,22 +2,25 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Convert static Pod files for control plane components into self-hosted DaemonSets configured via the Kubernetes API.
-->
将用于控制平面组件的静态 Pod 文件转换为通过 Kubernetes API 配置的自托管 DaemonSet。
<!--
See the documentation for self-hosting limitations.
-->
有关自托管的限制，请参阅相关文档。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 alpha 功能。
@@ -28,6 +31,7 @@ kubeadm alpha selfhosting pivot [flags]
<!--
### Examples
-->
### 示例
<!--
@@ -43,6 +47,7 @@ kubeadm alpha selfhosting pivot [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -137,11 +142,10 @@ kubeadm alpha selfhosting pivot [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_completion.md
+16 -9
View File
@@ -2,6 +2,7 @@
<!--
### Synopsis
-->
### 概要
<!--
@@ -10,12 +11,14 @@ The shell code must be evaluated to provide interactive
completion of kubeadm commands. This can be done by sourcing it from
the .bash_profile.
-->
为指定的 shell（bash 或 zsh）输出 shell 自动补全代码。
必须激活 shell 代码以提供交互式 kubeadm 命令补全。这可以通过加载 .bash_profile 文件完成。
<!--
Note: this requires the bash-completion framework.
-->
注意: 此功能依赖于 `bash-completion` 框架。
<!--
@@ -25,23 +28,30 @@ Once installed, bash_completion must be evaluated. This can be done by adding th
following line to the .bash_profile
$ source $(brew --prefix)/etc/bash_completion
-->
在 Mac 上使用 homebrew 安装:
```
brew install bash-completion
```
安装后，必须激活 bash_completion。这可以通过在 .bash_profile 文件中添加下面的命令行来完成
```
source $(brew --prefix)/etc/bash_completion
```
<!--
If bash-completion is not installed on Linux, please install the 'bash-completion' package
via your distribution's package manager.
-->
如果在 Linux 上没有安装 bash-completion，请通过您的发行版的包管理器安装 'bash-completion' 软件包。
如果在 Linux 上没有安装 bash-completion，请通过您的发行版的包管理器安装 `bash-completion` 软件包。
<!--
Note for zsh users: [1] zsh completions are only supported in versions of zsh &gt;= 5.2
-->
zsh 用户注意事项：[1] zsh 自动补全仅在 &gt;=v5.2 及以上版本中支持。
```
@@ -51,11 +61,10 @@ kubeadm completion SHELL [flags]
<!--
### Examples
-->
### 示例
<!--
```
# Install bash completion on a Mac using homebrew
brew install bash-completion
printf "\n# Bash completion support\nsource $(brew --prefix)/etc/bash_completion\n" >> $HOME/.bash_profile
@@ -71,7 +80,6 @@ source $HOME/.bash_profile
# Load the kubeadm completion code for zsh[1] into the current shell
source <(kubeadm completion zsh)
```
-->
```
@@ -94,6 +102,7 @@ source <(kubeadm completion zsh)
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -108,9 +117,7 @@ source <(kubeadm completion zsh)
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for completion
-->
<!-- help for completion -->
completion 操作的帮助命令
</td>
</tr>
@@ -118,11 +125,10 @@ source <(kubeadm completion zsh)
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -146,3 +152,4 @@ source <(kubeadm completion zsh)
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config.md
+17 -18
View File
@@ -2,19 +2,22 @@
<!--
### Synopsis
-->
### 概要
<!--
There is a ConfigMap in the kube-system namespace called "kubeadm-config" that kubeadm uses to store internal configuration about the
cluster. kubeadm CLI v1.8.0+ automatically creates this ConfigMap with the config used with 'kubeadm init', but if you
initialized your cluster using kubeadm v1.7.x or lower, you must use the 'config upload' command to create this
ConfigMap. This is required so that 'kubeadm upgrade' can configure your upgraded cluster correctly.
There is a ConfigMap in the kube-system namespace called "kubeadm-config" that kubeadm
uses to store internal configuration about the cluster. kubeadm CLI v1.8.0+ automatically
creates this ConfigMap with the config used with 'kubeadm init', but if you
initialized your cluster using kubeadm v1.7.x or lower, you must use the 'config upload'
command to create this ConfigMap. This is required so that 'kubeadm upgrade' can configure
your upgraded cluster correctly.
-->
kube-system 命名空间里有一个名为 "kubeadm-config" 的 ConfigMap，kubeadm 用它来存储有关集群的内部配置。
kubeadm CLI v1.8.0+ 通过一个配置自动创建该 ConfigMap，这个配置是和 'kubeadm init' 共用的。但是您如果使用 kubeadm v1.7.x 或更低的版本初始化集群，那么必须使用 'config upload' 命令创建该 ConfigMap。这是必要的操作，目的是使 'kubeadm upgrade' 能够正确地配置升级后的集群。
kube-system 命名空间里有一个名为 "kubeadm-config" 的 ConfigMap，kubeadm 用它来存储有关集群的内部配置。
kubeadm CLI v1.8.0+ 通过一个配置自动创建该 ConfigMap，这个配置是和 'kubeadm init' 共用的。
但是您如果使用 kubeadm v1.7.x 或更低的版本初始化集群，那么必须使用 'config upload' 命令创建该 ConfigMap。
这是必要的操作，目的是使 'kubeadm upgrade' 能够正确地配置升级后的集群。
```
kubeadm config [flags]
@@ -23,6 +26,7 @@ kubeadm config [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -37,9 +41,7 @@ kubeadm config [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for config
-->
<!-- help for config -->
config 操作的帮助命令
</td>
</tr>
@@ -54,8 +56,8 @@ kubeadm config [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.
<!-- The kubeconfig file to use when talking to the cluster.
If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.
-->
用于和集群通信的 kubeconfig 文件。如果它没有被设置，那么 kubeadm 将会搜索一个已经存在于标准路径的 kubeconfig 文件
</td>
@@ -64,11 +66,10 @@ kubeadm config [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -83,9 +84,7 @@ kubeadm config [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 到 '真实' 主机根文件系统的路径。
</td>
</tr>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images.md
+4
View File
@@ -2,11 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
Interact with container images used by kubeadm.
-->
与 kubeadm 使用的容器镜像交互。
```
@@ -16,6 +18,7 @@ kubeadm config images [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -44,6 +47,7 @@ kubeadm config images [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_list.md
+4 -1
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Print a list of images kubeadm will use. The configuration file is used in case any images or image repositories are customized.
-->
打印 kubeadm 要使用的镜像列表。配置文件用于自定义任何镜像或镜像存储库。
```
@@ -17,6 +18,7 @@ kubeadm config images list [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -86,6 +88,7 @@ kubeadm config images list [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_pull.md
+4 -1
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Pull images used by kubeadm.
-->
拉取 kubeadm 使用的镜像。
```
@@ -17,6 +18,7 @@ kubeadm config images pull [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -114,6 +116,7 @@ kubeadm config images pull [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_migrate.md
+14 -15
View File
@@ -2,17 +2,18 @@
<!--
### Synopsis
-->
### 概要
<!--
This command lets you convert configuration objects of older versions to the latest supported version,
locally in the CLI tool without ever touching anything in the cluster.
In this version of kubeadm, the following API versions are supported:
- kubeadm.k8s.io/v1beta2
-->
此命令允许您在 CLI 工具中将本地旧版本的配置对象转换为最新支持的版本，而无需变更集群中的任何内容。在此版本的 kubeadm 中，支持以下 API 版本：
- kubeadm.k8s.io/v1beta2
<!--
@@ -21,13 +22,16 @@ So regardless of what version you pass to the --old-config parameter here, the A
read, deserialized, defaulted, converted, validated, and re-serialized when written to stdout or
--new-config if specified.
-->
因此，无论您在此处传递 --old-config 参数的版本是什么，当写入到 stdout 或 --new-config （如果已指定）时，都会读取、反序列化、默认、转换、验证和重新序列化 API 对象。
因此，无论您在此处传递 --old-config 参数的版本是什么，当写入到 stdout 或 --new-config （如果已指定）时，
都会读取、反序列化、默认、转换、验证和重新序列化 API 对象。
<!--
In other words, the output of this command is what kubeadm actually would read internally if you
submitted this file to "kubeadm init"
-->
换句话说，如果您将此文件传递给 "kubeadm init"，则该命令的输出就是 kubeadm 实际上在内部读取的内容
换句话说，如果您将此文件传递给 "kubeadm init"，则该命令的输出就是 kubeadm 实际上在内部读取的内容。
```
kubeadm config migrate [flags]
@@ -36,6 +40,7 @@ kubeadm config migrate [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -50,9 +55,7 @@ kubeadm config migrate [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for migrate
-->
<!-- help for migrate -->
migrate 操作的帮助信息
</td>
</tr>
@@ -84,11 +87,10 @@ kubeadm config migrate [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -100,9 +102,7 @@ kubeadm config migrate [flags]
<tr>
<td colspan="2">
<!--
--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"
-->
<!-- kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf" -->
--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值："/etc/kubernetes/admin.conf"
</td>
</tr>
@@ -120,12 +120,11 @@ kubeadm config migrate [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 到 '真实' 主机根文件系统的路径。
</td>
</tr>
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_print.md
+5 -5
View File
@@ -2,14 +2,14 @@
<!--
### Synopsis
-->
### 概要
<!--
This command prints configurations for subcommands provided.
For details, see: https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2
-->
此命令显示所提供子命令的配置。
有关详细信息，请参阅：https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta2
@@ -20,6 +20,7 @@ kubeadm config print [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -34,9 +35,7 @@ kubeadm config print [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for print
-->
<!-- help for print -->
print 操作的帮助命令
</td>
</tr>
@@ -49,6 +48,7 @@ kubeadm config print [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_print_init-defaults.md
+4 -5
View File
@@ -4,19 +4,18 @@
-->
### 概要
<!--
This command prints objects such as the default init configuration that is used for 'kubeadm init'.
-->
此命令打印对象，例如用于 'kubeadm init' 的默认 init 配置对象。
<!--
Note that sensitive values like the Bootstrap Token fields are replaced with placeholder values like {"abcdef.0123456789abcdef" "" "nil" &lt;nil&gt; [] []} in order to pass validation but
not perform the real computation for creating a token.
-->
请注意，Bootstrap Token 字段之类的敏感值已替换为 {"abcdef.0123456789abcdef" "" "nil" &lt;nil&gt; [] []} 之类的占位符值以通过验证，但不执行创建令牌的实际计算。
请注意，Bootstrap Token 字段之类的敏感值已替换为 {"abcdef.0123456789abcdef" "" "nil" &lt;nil&gt; [] []} 之类的占位符值以通过验证，但不执行创建令牌的实际计算。
```
kubeadm config print init-defaults [flags]
@@ -25,6 +24,7 @@ kubeadm config print init-defaults [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -61,11 +61,10 @@ kubeadm config print init-defaults [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_print_join-defaults.md
+6 -5
View File
@@ -2,21 +2,22 @@
<!--
### Synopsis
-->
### 概要
<!--
This command prints objects such as the default join configuration that is used for 'kubeadm join'.
-->
此命令打印对象，例如用于 'kubeadm join' 的默认 join 配置对象。
<!--
Note that sensitive values like the Bootstrap Token fields are replaced with placeholder values like {"abcdef.0123456789abcdef" "" "nil" &lt;nil&gt; [] []} in order to pass validation but
not perform the real computation for creating a token.
-->
请注意，诸如 Bootstrap Token 字段之类的敏感值已替换为 {"abcdef.0123456789abcdef" "" "nil" &lt;nil&gt; [] []} 之类的占位符值以通过验证，但不执行创建令牌的实际计算。
请注意，诸如启动引导令牌字段之类的敏感值已替换为 {"abcdef.0123456789abcdef" "" "nil" &lt;nil&gt; [] []}
之类的占位符值以通过验证，但不执行创建令牌的实际计算。
```
kubeadm config print join-defaults [flags]
@@ -25,6 +26,7 @@ kubeadm config print join-defaults [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -61,11 +63,10 @@ kubeadm config print join-defaults [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_view.md
+5 -7
View File
@@ -2,17 +2,15 @@
<!--
### Synopsis
-->
### 概要
<!--
Using this command, you can view the ConfigMap in the cluster where the configuration for kubeadm is located.
The configuration is located in the "kube-system" namespace in the "kubeadm-config" ConfigMap.
-->
使用此命令，可以查看 kubeadm 配置的集群中的 ConfigMap。
使用此命令，可以查看 kubeadm 配置的集群中的 ConfigMap。
该配置位于 "kube-system" 命名空间中的名为 "kubeadm-config" 的 ConfigMap 中。
@@ -23,6 +21,7 @@ kubeadm config view [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -50,6 +49,7 @@ kubeadm config view [flags]
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@@ -81,9 +81,7 @@ kubeadm config view [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 到 '真实' 主机根文件系统的路径。
</td>
</tr>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init.md
+6 -4
View File
@@ -2,18 +2,21 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Run this command in order to set up the Kubernetes control plane
-->
运行此命令来搭建 Kubernetes 控制平面节点。
<!--
The "init" command executes the following phases:
-->
"init" 命令执行以下阶段：
```
preflight Run pre-flight checks
kubelet-start Write kubelet settings and (re)start the kubelet
@@ -51,7 +54,6 @@ addon Install required addons for passing Conformance tests
/kube-proxy Install the kube-proxy addon to a Kubernetes cluster
```
```
kubeadm init [flags]
```
@@ -59,6 +61,7 @@ kubeadm init [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -406,11 +409,10 @@ kubeadm init [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase.md
+5 -6
View File
@@ -2,17 +2,19 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Use this command to invoke single phase of the init workflow
-->
使用此命令可以调用 init 工作流程的单个阶段
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -27,9 +29,7 @@ Use this command to invoke single phase of the init workflow
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for phase
-->
<!-- help for phase -->
phase 操作的帮助命令
</td>
</tr>
@@ -37,11 +37,10 @@ Use this command to invoke single phase of the init workflow
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选择项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用子命令列表。
```
@@ -17,6 +18,7 @@ kubeadm init phase addon [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -41,11 +43,10 @@ kubeadm init phase addon [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_all.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Install all the addons
-->
安装所有插件（addon）
```
@@ -17,6 +18,7 @@ kubeadm init phase addon all [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -202,11 +204,10 @@ kubeadm init phase addon all [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_coredns.md
+8 -13
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Install the CoreDNS addon components via the API server. Please note that although the DNS server is deployed, it will not be scheduled until CNI is installed.
-->
通过 API 服务器安装 CoreDNS 附加组件。请注意，即使 DNS 服务器已部署，在安装 CNI 之前 DNS 服务器不会被调度执行。
```
@@ -17,6 +18,7 @@ kubeadm init phase addon coredns [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -55,9 +57,7 @@ kubeadm init phase addon coredns [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for coredns
-->
<!-- help for coredns -->
coredns 操作的帮助命令
</td>
</tr>
@@ -106,9 +106,7 @@ kubeadm init phase addon coredns [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Choose a specific Kubernetes version for the control plane.
-->
<!-- Choose a specific Kubernetes version for the control plane. -->
为控制平面选择特定的 Kubernetes 版本。
</td>
</tr>
@@ -123,9 +121,7 @@ kubeadm init phase addon coredns [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Use alternative range of IP address for service VIPs.
-->
<!-- Use alternative range of IP address for service VIPs. -->
为服务 VIP 选择 IP 地址范围。
</td>
</tr>
@@ -140,9 +136,7 @@ kubeadm init phase addon coredns [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Use alternative domain for services, e.g. "myorg.internal".
-->
<!-- Use alternative domain for services, e.g. "myorg.internal". -->
服务使用其它的域名，例如："myorg.internal"。
</td>
</tr>
@@ -155,6 +149,7 @@ kubeadm init phase addon coredns [flags]
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_addon_kube-proxy.md
+4 -2
View File
@@ -2,11 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
Install the kube-proxy addon components via the API server.
-->
通过 API 服务器安装 kube-proxy 附加组件。
```
@@ -16,6 +18,7 @@ kubeadm init phase addon kube-proxy [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -156,11 +159,10 @@ kubeadm init phase addon kube-proxy [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_bootstrap-token.md
+6 -3
View File
@@ -2,17 +2,19 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Bootstrap tokens are used for establishing bidirectional trust between a node joining the cluster and a control-plane node.
-->
启动引导令牌（bootstrap token）用于在即将加入集群的节点和控制平面节点之间建立双向信任。
<!--
This command makes all the configurations required to make bootstrap tokens works and then creates an initial token.
-->
该命令使启动引导令牌（bootstrap token）所需的所有配置生效，然后创建初始令牌。
```
@@ -22,6 +24,7 @@ kubeadm init phase bootstrap-token [flags]
<!--
### Examples
-->
### 示例
<!--
@@ -36,6 +39,7 @@ kubeadm init phase bootstrap-token [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -101,11 +105,10 @@ kubeadm init phase bootstrap-token [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs.md
+5 -4
View File
@@ -2,13 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用子命令列表。
```
@@ -18,6 +18,7 @@ kubeadm init phase certs [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -42,11 +43,10 @@ kubeadm init phase certs [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父指令中继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -70,3 +70,4 @@ kubeadm init phase certs [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_all.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate all certificates
-->
生成所有证书
```
@@ -17,6 +18,7 @@ kubeadm init phase certs all [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -157,11 +159,10 @@ kubeadm init phase certs all [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver-etcd-client.md
+13 -24
View File
@@ -2,22 +2,25 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the certificate the apiserver uses to access etcd, and save them into apiserver-etcd-client.cert and apiserver-etcd-client.key files.
-->
生成 apiserver 用于访问 etcd 的证书，并将其保存到 apiserver-etcd-client.cert 和 apiserver-etcd-client.key 文件中。
<!--
If both files already exist, kubeadm skips the generation step and existing files will be used.
-->
如果两个文件都已存在，则 kubeadm 将跳过生成步骤，使用现有文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 Alpha 功能。
```
@@ -27,6 +30,7 @@ kubeadm init phase certs apiserver-etcd-client [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -46,9 +50,7 @@ kubeadm init phase certs apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path where to save and store the certificates.
-->
<!-- The path where to save and store the certificates. -->
证书的存储路径。
</td>
</tr>
@@ -58,9 +60,7 @@ kubeadm init phase certs apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Path to a kubeadm configuration file.
-->
<!-- Path to a kubeadm configuration file. -->
kubeadm 配置文件的路径。
</td>
</tr>
@@ -70,9 +70,7 @@ kubeadm init phase certs apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path to output the CSRs and private keys to
-->
<!-- The path to output the CSRs and private keys to -->
输出 CSR 和私钥的路径
</td>
</td>
@@ -83,9 +81,7 @@ kubeadm init phase certs apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Create CSRs instead of generating certificates
-->
<!-- Create CSRs instead of generating certificates -->
创建 CSR 而不是生成证书
</td>
</tr>
@@ -95,18 +91,14 @@ kubeadm init phase certs apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for apiserver-etcd-client
-->
<!-- help for apiserver-etcd-client -->
apiserver-etcd-client 操作的帮助命令
</td>
</tr>
<tr>
<td colspan="2">
<!--
--kubernetes-version string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "stable-1"
-->
<!-- kubernetes-version string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "stable-1" -->
--kubernetes-version string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值："stable-1"
</td>
</tr>
@@ -122,11 +114,10 @@ kubeadm init phase certs apiserver-etcd-client [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@@ -141,9 +132,7 @@ kubeadm init phase certs apiserver-etcd-client [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 到 '真实' 主机根文件系统的路径。
</td>
</tr>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver-kubelet-client.md
+6 -4
View File
@@ -2,22 +2,25 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the certificate for the API server to connect to kubelet, and save them into apiserver-kubelet-client.cert and apiserver-kubelet-client.key files.
-->
生成供 API 服务器连接 kubelet 的证书，并将其保存到 apiserver-kubelet-client.cert 和 apiserver-kubelet-client.key 文件中。
<!--
If both files already exist, kubeadm skips the generation step and existing files will be used.
-->
如果两个文件都已存在，则 kubeadm 将跳过生成步骤，使用现有文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 Alpha 功能。
```
@@ -27,6 +30,7 @@ kubeadm init phase certs apiserver-kubelet-client [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -121,11 +125,10 @@ kubeadm init phase certs apiserver-kubelet-client [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@@ -150,4 +153,3 @@ kubeadm init phase certs apiserver-kubelet-client [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver.md
+7 -4
View File
@@ -2,28 +2,31 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the certificate for serving the Kubernetes API, and save them into apiserver.cert and apiserver.key files.
-->
生成用于服务 Kubernetes API 的证书，并将其保存到 apiserver.cert 和 apiserver.key 文件中。
<!--
Default SANs are kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, 10.96.0.1, 127.0.0.1
-->
默认 SAN 是 kubernetes、kubernetes.default、kubernetes.default.svc、kubernetes.default.svc.cluster.local、10.96.0.1、127.0.0.1。
<!--
If both files already exist, kubeadm skips the generation step and existing files will be used.
-->
如果两个文件都已存在，则 kubeadm 将跳过生成步骤，使用现有文件。
如果两个文件都已存在，则 kubeadm 将跳过生成步骤，使用现有文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 Alpha 功能。
```
@@ -33,6 +36,7 @@ kubeadm init phase certs apiserver [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -197,11 +201,10 @@ kubeadm init phase certs apiserver [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_ca.md
+6 -3
View File
@@ -2,22 +2,25 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components, and save them into ca.cert and ca.key files.
-->
生成自签名的 Kubernetes CA 以提供其他 Kubernetes 组件的身份，并将其保存到 ca.cert 和 ca.key 文件中。
<!--
If both files already exist, kubeadm skips the generation step and existing files will be used.
-->
如果两个文件都已存在，则 kubeadm 将跳过生成步骤，使用现有文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 Alpha 功能。
```
@@ -27,6 +30,7 @@ kubeadm init phase certs ca [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -97,11 +101,10 @@ kubeadm init phase certs ca [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-ca.md
+6 -4
View File
@@ -2,22 +2,25 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the self-signed CA to provision identities for etcd, and save them into etcd/ca.cert and etcd/ca.key files.
-->
生成用于为 etcd 设置身份的自签名 CA，并将其保存到 etcd/ca.cert 和 etcd/ca.key 文件中。
<!--
If both files already exist, kubeadm skips the generation step and existing files will be used.
-->
如果两个文件都已存在，则 kubeadm 将跳过生成步骤，使用现有文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 Alpha 功能。
```
@@ -27,6 +30,7 @@ kubeadm init phase certs etcd-ca [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -97,11 +101,10 @@ kubeadm init phase certs etcd-ca [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@@ -126,4 +129,3 @@ kubeadm init phase certs etcd-ca [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-healthcheck-client.md
+6 -3
View File
@@ -2,22 +2,25 @@
<!--
### Synopsis
-->
### 概要
<!--
Generate the certificate for liveness probes to healthcheck etcd, and save them into etcd/healthcheck-client.cert and etcd/healthcheck-client.key files.
-->
生成用于 etcd 健康检查的活跃性探针的证书，并将其保存到 healthcheck-client.cert 和 etcd/healthcheck-client.key 文件中。
生成用于 etcd 健康检查的活跃性探针的证书，并将其保存到 healthcheck-client.cert 和 etcd/healthcheck-client.key 文件中。
<!--
If both files already exist, kubeadm skips the generation step and existing files will be used.
-->
如果两个文件都已存在，则 kubeadm 将跳过生成步骤，使用现有文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 alpha 功能。
```
@@ -27,6 +30,7 @@ kubeadm init phase certs etcd-healthcheck-client [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -118,11 +122,10 @@ kubeadm init phase certs etcd-healthcheck-client [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-peer.md
+13 -22
View File
@@ -2,27 +2,31 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the certificate for etcd nodes to communicate with each other, and save them into etcd/peer.cert and etcd/peer.key files.
-->
生成 etcd 节点相互通信的证书，并将其保存到 etcd/peer.cert 和 etcd/peer.key 文件中。
<!--
Default SANs are localhost, 127.0.0.1, 127.0.0.1, ::1
-->
默认 SAN 为 localhost、127.0.0.1、127.0.0.1、:: 1
<!--
If both files already exist, kubeadm skips the generation step and existing files will be used.
-->
如果两个文件都已存在，则 kubeadm 将跳过生成步骤，使用现有文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 alpha 功能。
```
@@ -32,6 +36,7 @@ kubeadm init phase certs etcd-peer [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -51,9 +56,7 @@ kubeadm init phase certs etcd-peer [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path where to save and store the certificates.
-->
<!-- The path where to save and store the certificates. -->
保存和存储证书的路径。
</td>
</tr>
@@ -63,9 +66,7 @@ kubeadm init phase certs etcd-peer [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Path to kubeadm configuration file.
-->
<!-- Path to kubeadm configuration file. -->
kubeadm 配置文件的路径。
</td>
</tr>
@@ -75,9 +76,7 @@ kubeadm init phase certs etcd-peer [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path to output the CSRs and private keys to
-->
<!-- The path to output the CSRs and private keys to -->
输出 CSR 和私钥的路径
</td>
</tr>
@@ -87,9 +86,7 @@ kubeadm init phase certs etcd-peer [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Create CSRs instead of generating certificates
-->
<!-- Create CSRs instead of generating certificates -->
创建 CSR 而不是生成证书
</td>
</tr>
@@ -99,9 +96,7 @@ kubeadm init phase certs etcd-peer [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for etcd-peer
-->
<!-- help for etcd-peer -->
etcd-peer 操作的帮助命令
</td>
</tr>
@@ -116,9 +111,7 @@ kubeadm init phase certs etcd-peer [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Choose a specific Kubernetes version for the control plane.
-->
<!-- Choose a specific Kubernetes version for the control plane. -->
为控制平面指定特定的 Kubernetes 版本。
</td>
</tr>
@@ -126,11 +119,10 @@ kubeadm init phase certs etcd-peer [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@@ -155,4 +147,3 @@ kubeadm init phase certs etcd-peer [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-server.md
-1
View File
@@ -155,4 +155,3 @@ kubeadm init phase certs etcd-server [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_front-proxy-ca.md
+6 -3
View File
@@ -2,22 +2,25 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the self-signed CA to provision identities for front proxy, and save them into front-proxy-ca.cert and front-proxy-ca.key files.
-->
生成自签名 CA 来提供前端代理的身份，并将其保存到 front-proxy-ca.cert 和 front-proxy-ca.key 文件中。
<!--
If both files already exist, kubeadm skips the generation step and existing files will be used.
-->
如果两个文件都已存在，kubeadm 将跳过生成步骤并将使用现有文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令目前是 alpha 阶段。
```
@@ -27,6 +30,7 @@ kubeadm init phase certs front-proxy-ca [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -97,11 +101,10 @@ kubeadm init phase certs front-proxy-ca [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_front-proxy-client.md
+4 -7
View File
@@ -2,20 +2,17 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the certificate for the front proxy client, and save them into front-proxy-client.cert and front-proxy-client.key files.
If both files already exist, kubeadm skips the generation step and existing files will be used.
Alpha Disclaimer: this command is currently alpha.
-->
为前端代理客户端生成证书，并将其保存到 front-proxy-client.cert 和 front-proxy-client.key 文件中。
如果两个文件都已存在，kubeadm 将跳过生成步骤并将使用现有文件。
Alpha 免责声明：此命令目前是 alpha 阶段。
```
@@ -25,6 +22,7 @@ kubeadm init phase certs front-proxy-client [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -118,11 +116,10 @@ kubeadm init phase certs front-proxy-client [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_sa.md
+6 -6
View File
@@ -2,26 +2,27 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the private key for signing service account tokens along with its public key, and save them into sa.key and sa.pub files. If both files already exist, kubeadm skips the generation step and existing files will be used.
-->
生成用于签名 service account 令牌的私钥及其公钥，并将其保存到 sa.key 和 sa.pub 文件中。如果两个文件都已存在，则 kubeadm 会跳过生成步骤，而将使用现有文件。
<!--
Alpha Disclaimer: this command is currently alpha.
-->
Alpha 免责声明：此命令当前为 alpha 阶段。
```
kubeadm init phase certs sa [flags]
```
<!--
### Options
-->
<!-- ### Options -->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -63,11 +64,10 @@ kubeadm init phase certs sa [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane.md
+6 -9
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用子命令列表。
```
@@ -17,6 +18,7 @@ kubeadm init phase control-plane [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -31,9 +33,7 @@ kubeadm init phase control-plane [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for control-plane
-->
<!-- help for control-plane -->
control-plane 操作的帮助命令
</td>
</tr>
@@ -41,11 +41,10 @@ kubeadm init phase control-plane [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@@ -60,9 +59,7 @@ kubeadm init phase control-plane [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 到 '真实' 主机根文件系统的路径。
</td>
</td>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_all.md
+5
View File
@@ -2,11 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
Generate all static Pod manifest files
-->
生成所有的静态 Pod 清单文件
```
@@ -21,6 +23,7 @@ kubeadm init phase control-plane all [flags]
# functionally equivalent to what is generated by kubeadm init.
# Generates all static Pod manifest files using options read from a configuration file.
-->
### 示例
```
@@ -34,6 +37,7 @@ kubeadm init phase control-plane all --config config.yaml
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -254,6 +258,7 @@ kubeadm init phase control-plane all --config config.yaml
<!--
### Options inherited from parent commands
-->
### 从父指令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_apiserver.md
+4 -2
View File
@@ -1,12 +1,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generates the kube-apiserver static Pod manifest
-->
生成 kube-apiserver 静态 Pod 清单
```
@@ -16,6 +17,7 @@ kubeadm init phase control-plane apiserver [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -201,8 +203,8 @@ kubeadm init phase control-plane apiserver [flags]
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
<colgroup>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_controller-manager.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generates the kube-controller-manager static Pod manifest
-->
生成 kube-controller-manager 静态 Pod 清单
```
@@ -17,6 +18,7 @@ kubeadm init phase control-plane controller-manager [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -140,11 +142,10 @@ kubeadm init phase control-plane controller-manager [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_scheduler.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generates the kube-scheduler static Pod manifest
-->
生成 kube-scheduler 静态 Pod 清单
```
@@ -17,6 +18,7 @@ kubeadm init phase control-plane scheduler [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -128,11 +130,10 @@ kubeadm init phase control-plane scheduler [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_etcd.md
+6 -5
View File
@@ -2,11 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用子命令列表。
```
@@ -16,6 +18,7 @@ kubeadm init phase etcd [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -30,9 +33,7 @@ kubeadm init phase etcd [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for etcd
-->
<!-- help for etcd -->
etcd 操作的帮助命令
</td>
</tr>
@@ -40,11 +41,10 @@ kubeadm init phase etcd [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@@ -68,3 +68,4 @@ kubeadm init phase etcd [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_etcd_local.md
+11 -21
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the static Pod manifest file for a local, single-node local etcd instance
-->
为本地单节点 etcd 实例生成静态 Pod 清单文件
```
@@ -17,6 +18,7 @@ kubeadm init phase etcd local [flags]
<!--
### Examples
-->
### 示例
<!--
@@ -37,6 +39,7 @@ kubeadm init phase etcd local --config config.yaml
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -56,9 +59,7 @@ kubeadm init phase etcd local --config config.yaml
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path where to save and store the certificates.
-->
<!-- The path where to save and store the certificates. -->
存储证书的路径。
</td>
</tr>
@@ -68,9 +69,7 @@ kubeadm init phase etcd local --config config.yaml
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Path to a kubeadm configuration file.
-->
<!-- Path to a kubeadm configuration file. -->
kubeadm 配置文件的路径。
</td>
</tr>
@@ -80,9 +79,7 @@ kubeadm init phase etcd local --config config.yaml
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path where kustomize patches for static pod manifests are stored.
-->
<!-- The path where kustomize patches for static pod manifests are stored. -->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。
</td>
</tr>
@@ -92,9 +89,7 @@ kubeadm init phase etcd local --config config.yaml
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for local
-->
<!-- help for local -->
local 操作的帮助命令
</td>
</tr>
@@ -109,9 +104,7 @@ kubeadm init phase etcd local --config config.yaml
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Choose a container registry to pull control plane images from
-->
<!-- Choose a container registry to pull control plane images from -->
选择要从中拉取控制平面镜像的容器仓库
</td>
</tr>
@@ -119,11 +112,10 @@ kubeadm init phase etcd local --config config.yaml
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@@ -138,9 +130,7 @@ kubeadm init phase etcd local --config config.yaml
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 到 '真实' 主机根文件系统的路径。
</td>
</tr>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请阅读可用子命令列表。
```
@@ -17,6 +18,7 @@ kubeadm init phase kubeconfig [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -41,11 +43,10 @@ kubeadm init phase kubeconfig [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_admin.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the kubeconfig file for the admin and for kubeadm itself, and save it to admin.conf file.
-->
为管理员和 kubeadm 本身生成 kubeconfig 文件，并将其保存到 admin.conf 文件中。
```
@@ -17,6 +18,7 @@ kubeadm init phase kubeconfig admin [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -145,11 +147,10 @@ kubeadm init phase kubeconfig admin [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_all.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate all kubeconfig files
-->
生成所有 kubeconfig 文件
```
@@ -17,6 +18,7 @@ kubeadm init phase kubeconfig all [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -157,11 +159,10 @@ kubeadm init phase kubeconfig all [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_controller-manager.md
+6 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the kubeconfig file for the controller manager to use and save it to controller-manager.conf file
-->
生成控制器管理器要使用的 kubeconfig 文件，并保存到 controller-manager.conf 文件中。
```
@@ -17,6 +18,7 @@ kubeadm init phase kubeconfig controller-manager [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -141,12 +143,13 @@ kubeadm init phase kubeconfig controller-manager [flags]
为控制平面指定特定的 Kubernetes 版本。
</td>
</tr>
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_kubelet.md
+4 -6
View File
@@ -4,17 +4,17 @@
-->
### 概要
<!--
Generate the kubeconfig file for the kubelet to use and save it to kubelet.conf file.
-->
生成 kubelet 要使用的 kubeconfig 文件，并将其保存到 kubelet.conf 文件。
<!--
Please note that this should *only* be used for cluster bootstrapping purposes. After your control plane is up, you should request all kubelet credentials from the CSR API.
-->
请注意，该操作目的是*仅*应用于引导集群。在控制平面启动之后，应该从 CSR API 请求所有 kubelet 凭据。
请注意，该操作目的是*仅*应用于引导集群。在控制平面启动之后，应该从 CSR API 请求所有 kubelet 凭据。
```
kubeadm init phase kubeconfig kubelet [flags]
@@ -23,6 +23,7 @@ kubeadm init phase kubeconfig kubelet [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -163,11 +164,10 @@ kubeadm init phase kubeconfig kubelet [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
@@ -192,5 +192,3 @@ kubeadm init phase kubeconfig kubelet [flags]
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubeconfig_scheduler.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the kubeconfig file for the scheduler to use and save it to scheduler.conf file.
-->
生成调度器（scheduler）要使用的 kubeconfig 文件，并保存到 scheduler.conf 文件中。
```
@@ -17,6 +18,7 @@ kubeadm init phase kubeconfig scheduler [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -145,11 +147,10 @@ kubeadm init phase kubeconfig scheduler [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubelet-start.md
+6 -2
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Write a file with KubeletConfiguration and an environment file with node specific kubelet settings, and then (re)start kubelet.
-->
使用 kubelet 配置文件编写一个文件，并使用特定节点的 kubelet 设置编写一个环境文件，然后（重新）启动 kubelet。
```
@@ -17,7 +18,9 @@ kubeadm init phase kubelet-start [flags]
<!--
### Examples
-->
### 示例
<!--
# Writes a dynamic environment file with kubelet flags from a InitConfiguration file.
-->
@@ -30,6 +33,7 @@ kubeadm init phase kubelet-start [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -90,10 +94,10 @@ kubeadm init phase kubelet-start [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_mark-control-plane.md
+5 -7
View File
@@ -2,14 +2,14 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Mark a node as a control-plane
-->
标记 Node 节点为控制平面节点
标记 Node 节点为控制平面节点
```
kubeadm init phase mark-control-plane [flags]
@@ -17,13 +17,11 @@ kubeadm init phase mark-control-plane [flags]
<!--
### Examples
-->
<!--
# Applies control-plane label and taint to the current node, functionally equivalent to what executed by kubeadm init.
# Applies control-plane label and taint to a specific node
-->
### 示例
```
@@ -37,6 +35,7 @@ kubeadm init phase mark-control-plane [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -85,11 +84,10 @@ kubeadm init phase mark-control-plane [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_preflight.md
+5 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Run pre-flight checks for kubeadm init.
-->
运行 kubeadm init 前的启动检查。
```
@@ -17,6 +18,7 @@ kubeadm init phase preflight [flags]
<!--
### Examples
-->
### 案例
<!--
@@ -31,6 +33,7 @@ kubeadm init phase preflight [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -79,11 +82,10 @@ kubeadm init phase preflight [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 继承于父命令的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-certs.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用子命令列表。
```
@@ -17,6 +18,7 @@ kubeadm init phase upload-certs [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -89,11 +91,10 @@ kubeadm init phase upload-certs [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config.md
+3
View File
@@ -2,11 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
This command is not meant to be run on its own. See list of available subcommands.
-->
此命令并非设计用来单独运行。请参阅可用的子命令列表。
```
@@ -44,6 +46,7 @@ kubeadm init phase upload-config [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_all.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Upload all configuration to a config map
-->
将所有配置上传到 ConfigMap
```
@@ -17,6 +18,7 @@ kubeadm init phase upload-config all [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -71,11 +73,10 @@ kubeadm init phase upload-config all [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubeadm.md
+9 -4
View File
@@ -2,17 +2,20 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Upload the kubeadm ClusterConfiguration to a ConfigMap called kubeadm-config in the kube-system namespace. This enables correct configuration of system components and a seamless user experience when upgrading.
-->
将 kubeadm ClusterConfiguration 上传到 kube-system 命名空间中名为 kubeadm-config 的 ConfigMap 中。这样就可以正确配置系统组件，并在升级时提供无缝的用户体验。
将 kubeadm ClusterConfiguration 上传到 kube-system 命名空间中名为 kubeadm-config 的 ConfigMap 中。
这样就可以正确配置系统组件，并在升级时提供无缝的用户体验。
<!--
Alternatively, you can use kubeadm config.
-->
另外，可以使用 kubeadm 配置。
```
@@ -22,11 +25,13 @@ kubeadm init phase upload-config kubeadm [flags]
<!--
### Examples
-->
### 示例
<!--
# upload the configuration of your cluster
-->
```
# 上传集群配置
kubeadm init phase upload-config --config=myConfig.yaml
@@ -35,6 +40,7 @@ kubeadm init phase upload-config --config=myConfig.yaml
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -88,11 +94,10 @@ kubeadm init phase upload-config --config=myConfig.yaml
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_upload-config_kubelet.md
+12 -13
View File
@@ -2,13 +2,15 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Upload kubelet configuration extracted from the kubeadm InitConfiguration object to a ConfigMap of the form kubelet-config-1.X in the cluster, where X is the minor version of the current (API Server) Kubernetes version.
-->
将从 kubeadm InitConfiguration 对象提取的 kubelet 配置上传到集群中 kubelet-config-1.X 形式的 ConfigMap，其中 X 是当前（API 服务器）Kubernetes 版本的次要版本。
将从 kubeadm InitConfiguration 对象提取的 kubelet 配置上传到集群中 kubelet-config-1.X 形式的
ConfigMap，其中 X 是当前（API 服务器）Kubernetes 版本的次要版本。
```
kubeadm init phase upload-config kubelet [flags]
@@ -17,6 +19,7 @@ kubeadm init phase upload-config kubelet [flags]
<!--
### Examples
-->
### 示例
<!--
@@ -25,6 +28,7 @@ kubeadm init phase upload-config kubelet [flags]
kubeadm init phase upload-config kubelet --config kubeadm.yaml
```
-->
```
# 将 kubelet 配置从 kubeadm 配置文件上传到集群中的 ConfigMap。
kubeadm init phase upload-config kubelet --config kubeadm.yaml
@@ -33,6 +37,7 @@ kubeadm init phase upload-config kubelet --config kubeadm.yaml
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -47,9 +52,7 @@ kubeadm init phase upload-config kubelet --config kubeadm.yaml
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Path to a kubeadm configuration file.
-->
<!-- Path to a kubeadm configuration file. -->
到 kubeadm 配置文件的路径。
</td>
</tr>
@@ -59,18 +62,14 @@ kubeadm init phase upload-config kubelet --config kubeadm.yaml
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for kubelet
-->
<!-- help for kubelet -->
kubelet 操作的帮助命令
</td>
</tr>
<tr>
<td colspan="2">
<!--
--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"
-->
<!-- kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf" -->
--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值："/etc/kubernetes/admin.conf"</td>
</tr>
<tr>
@@ -85,11 +84,10 @@ kubeadm init phase upload-config kubelet --config kubeadm.yaml
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -113,3 +111,4 @@ kubeadm init phase upload-config kubelet --config kubeadm.yaml
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join.md
+6 -5
View File
@@ -4,14 +4,13 @@
-->
### 摘要
<!--
When joining a kubeadm initialized cluster, we need to establish
bidirectional trust. This is split into discovery (having the Node
trust the Kubernetes Control Plane) and TLS bootstrap (having the Kubernetes
Control Plane trust the Node).
-->
当节点加入 kubeadm 初始化的集群时，我们需要建立双向信任。
这个过程可以分解为发现（让待加入节点信任 Kubernetes 控制平面节点）和 TLS 引导（让Kubernetes 控制平面节点信任待加入节点）两个部分。
@@ -27,11 +26,12 @@ the discovery information is loaded from a URL, HTTPS must be used.
Also, in that case the host installed CA bundle is used to verify
the connection.
-->
有两种主要的发现方案。
第一种方法是使用共享令牌和 API 服务器的 IP 地址。
第二种是提供一个文件 - 标准 kubeconfig 文件的一个子集。
该文件可以是本地文件，也可以通过 HTTPS URL 下载。
格式是 kubeadm join --discovery-token abcdef.1234567890abcdef 1.2.3.4:6443、kubeadm join--discovery-file path/to/file.conf、或者 kubeadm join --discovery-file `https://url/file.conf`。
格式是 `kubeadm join --discovery-token abcdef.1234567890abcdef 1.2.3.4:6443`、`kubeadm join--discovery-file path/to/file.conf` 或者`kubeadm join --discovery-file https://url/file.conf`。
只能使用其中一种。
如果发现信息是从 URL 加载的，必须使用 HTTPS。
此外，在这种情况下，主机安装的 CA 包用于验证连接。
@@ -80,11 +80,12 @@ TLS 引导机制也通过共享令牌驱动。
通常两个部分会使用相同的令牌。
在这种情况下可以使用 --token 参数，而不是单独指定每个令牌。
<!--
The "join [api-server-endpoint]" command executes the following phases:
-->
"join [api-server-endpoint]" 命令执行下列阶段：
```
preflight Run join pre-flight checks
control-plane-prepare Prepare the machine for serving a control plane
@@ -114,7 +115,6 @@ kubeadm join [api-server-endpoint] [flags]
<col span="1" />
</colgroup>
<tbody>
<tr>
<td colspan="2">--apiserver-advertise-address string</td>
</tr>
@@ -331,6 +331,7 @@ kubeadm join [api-server-endpoint] [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase.md
+6 -9
View File
@@ -2,17 +2,19 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Use this command to invoke single phase of the join workflow
-->
使用此命令来调用 `join` 工作流程的某个阶段
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -27,9 +29,7 @@ Use this command to invoke single phase of the join workflow
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for phase
-->
<!-- help for phase -->
phase 操作的帮助命令
</td>
</tr>
@@ -37,11 +37,10 @@ Use this command to invoke single phase of the join workflow
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -56,9 +55,7 @@ Use this command to invoke single phase of the join workflow
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 指向 '真实' 宿主机根文件系统的路径。
</td>
</tr>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join.md
+6 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Join a machine as a control plane instance
-->
添加作为控制平面实例的机器
```
@@ -17,6 +18,7 @@ kubeadm join phase control-plane-join [flags]
<!--
### Examples
-->
### 示例
<!--
@@ -25,6 +27,7 @@ kubeadm join phase control-plane-join [flags]
kubeadm join phase control-plane-join all
```
-->
```
# 将机器作为控制平面实例加入
kubeadm join phase control-plane-join all
@@ -33,6 +36,7 @@ kubeadm join phase control-plane-join all
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -57,11 +61,10 @@ kubeadm join phase control-plane-join all
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_all.md
+4 -2
View File
@@ -2,11 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
Joins a machine as a control plane instance
-->
添加作为控制平面实例的机器
```
@@ -16,6 +18,7 @@ kubeadm join phase control-plane-join all [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -88,11 +91,10 @@ kubeadm join phase control-plane-join all [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_etcd.md
+4
View File
@@ -2,11 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
Add a new local etcd member
-->
添加新的本地 etcd 成员
```
@@ -16,6 +18,7 @@ kubeadm join phase control-plane-join etcd [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -103,6 +106,7 @@ kubeadm join phase control-plane-join etcd [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_mark-control-plane.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Mark a node as a control-plane
-->
将 Node 节点标记为控制平面节点
```
@@ -17,6 +18,7 @@ kubeadm join phase control-plane-join mark-control-plane [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -77,11 +79,10 @@ kubeadm join phase control-plane-join mark-control-plane [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-join_update-status.md
+9 -15
View File
@@ -2,11 +2,13 @@
<!--
### Synopsis
-->
## 概要
<!--
Register the new control-plane node into the ClusterStatus maintained in the kubeadm-config ConfigMap
-->
将新的控制平面节点注册到 kubeadm-config ConfigMap 维护的 ClusterStatus 中
```
@@ -16,6 +18,7 @@ kubeadm join phase control-plane-join update-status [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -42,9 +45,7 @@ kubeadm join phase control-plane-join update-status [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Path to kubeadm config file.
-->
<!-- Path to kubeadm config file. -->
kubeadm 配置文件的路径。
</td>
</tr>
@@ -54,9 +55,7 @@ kubeadm join phase control-plane-join update-status [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Create a new control plane instance on this node
-->
<!-- Create a new control plane instance on this node -->
在此节点上创建一个新的控制平面实例
</td>
</tr>
@@ -66,9 +65,7 @@ kubeadm join phase control-plane-join update-status [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for update-status
-->
<!-- help for update-status -->
update-status 操作的帮助命令
</td>
</tr>
@@ -78,9 +75,7 @@ kubeadm join phase control-plane-join update-status [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Specify the node name.
-->
<!-- Specify the node name. -->
指定节点名称。
</td>
</tr>
@@ -93,6 +88,7 @@ kubeadm join phase control-plane-join update-status [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -107,9 +103,7 @@ kubeadm join phase control-plane-join update-status [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 到 '真实' 主机根文件系统的路径。
</td>
</tr>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare.md
+5 -2
View File
@@ -2,11 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
Prepare the machine for serving a control plane
-->
准备为控制平面服务的机器
```
@@ -19,6 +21,7 @@ kubeadm join phase control-plane-prepare [flags]
<!--
# Prepares the machine for serving a control plane
-->
### 示例
```
@@ -29,6 +32,7 @@ kubeadm join phase control-plane-prepare all
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -53,11 +57,10 @@ kubeadm join phase control-plane-prepare all
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_all.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Prepare the machine for serving a control plane
-->
准备为控制平面服务的机器
```
@@ -17,6 +18,7 @@ kubeadm join phase control-plane-prepare all [api-server-endpoint] [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -202,11 +204,10 @@ kubeadm join phase control-plane-prepare all [api-server-endpoint] [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_certs.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the certificates for the new control plane components
-->
为新的控制平面组件生成证书
```
@@ -17,6 +18,7 @@ kubeadm join phase control-plane-prepare certs [api-server-endpoint] [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -161,11 +163,10 @@ kubeadm join phase control-plane-prepare certs [api-server-endpoint] [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_control-plane.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Generate the manifests for the new control plane components
-->
为新的控制平面组件生成清单（manifest）
```
@@ -17,6 +18,7 @@ kubeadm join phase control-plane-prepare control-plane [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -106,11 +108,10 @@ kubeadm join phase control-plane-prepare control-plane [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_download-certs.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
[EXPERIMENTAL] Download certificates shared among control-plane nodes from the kubeadm-certs Secret
-->
[实验]从 kubeadm-certs Secret 下载控制平面节点之间共享的证书
```
@@ -17,6 +18,7 @@ kubeadm join phase control-plane-prepare download-certs [api-server-endpoint] [f
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -149,11 +151,10 @@ kubeadm join phase control-plane-prepare download-certs [api-server-endpoint] [f
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_kubeconfig.md
+3 -3
View File
@@ -4,10 +4,10 @@
-->
### 概要
<!--
Generate the kubeconfig for the new control plane components
-->
为新的控制平面组件生成 kubeconfig
```
@@ -17,6 +17,7 @@ kubeadm join phase control-plane-prepare kubeconfig [api-server-endpoint] [flags
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -149,11 +150,10 @@ kubeadm join phase control-plane-prepare kubeconfig [api-server-endpoint] [flags
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令中继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_kubelet-start.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Write a file with KubeletConfiguration and an environment file with node specific kubelet settings, and then (re)start kubelet.
-->
生成一个包含 KubeletConfiguration 的文件和一个包含特定于节点的 kubelet 配置的环境文件，然后（重新）启动 kubelet。
```
@@ -17,6 +18,7 @@ kubeadm join phase kubelet-start [api-server-endpoint] [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -150,11 +152,10 @@ kubeadm join phase kubelet-start [api-server-endpoint] [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_preflight.md
+7 -7
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Run pre-flight checks for kubeadm join.
-->
运行 kubeadm join 命令添加节点前检查。
```
@@ -16,20 +17,20 @@ kubeadm join phase preflight [api-server-endpoint] [flags]
<!--
### Examples
-->
### 示例
<!--
# Run join pre-flight checks using a config file.
-->
### 示例
```
＃使用配置文件运行 kubeadm join 命令添加节点前检查。
# 使用配置文件运行 kubeadm join 命令添加节点前检查。
kubeadm join phase preflight --config kubeadm-config.yml
```
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -227,11 +228,10 @@ kubeadm join phase preflight [api-server-endpoint] [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset.md
+7 -5
View File
@@ -1,19 +1,21 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Performs a best effort revert of changes made to this host by 'kubeadm init' or 'kubeadm join'
-->
尽最大努力还原通过 'kubeadm init' 或者 'kubeadm join' 操作对主机所做的更改
<!--
The "reset" command executes the following phases:
-->
"reset" 命令执行以下阶段：
```
preflight Run reset pre-flight checks
update-cluster-status Remove this node from the ClusterStatus object.
@@ -28,6 +30,7 @@ kubeadm reset [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -124,9 +127,7 @@ kubeadm reset [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
List of phases to be skipped
-->
<!-- List of phases to be skipped -->
要跳过的阶段列表
</td>
</tr>
@@ -139,6 +140,7 @@ kubeadm reset [flags]
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase.md
+4 -4
View File
@@ -2,17 +2,19 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Use this command to invoke single phase of the reset workflow
-->
使用此命令来调用 `reset` 工作流程的某个阶段
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -37,11 +39,10 @@ Use this command to invoke single phase of the reset workflow
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -66,4 +67,3 @@ Use this command to invoke single phase of the reset workflow
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase_cleanup-node.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Run cleanup node.
-->
执行 cleanup node（清理节点）操作。
```
@@ -17,6 +18,7 @@ kubeadm reset phase cleanup-node [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -70,11 +72,10 @@ kubeadm reset phase cleanup-node [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase_preflight.md
+4 -3
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Run pre-flight checks for kubeadm reset.
-->
kubeadm reset（重置）前运行启动前检查。
```
@@ -17,6 +18,7 @@ kubeadm reset phase preflight [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -65,11 +67,10 @@ kubeadm reset phase preflight [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase_remove-etcd-member.md
+4 -22
View File
@@ -1,19 +1,13 @@
<!--
Upload configuration about the current state, so that 'kubeadm upgrade' can later know how to configure the upgraded cluster.
-->
上传关于当前状态的配置，以便 'kubeadm upgrade' 以后可以知道如何配置升级后的集群。
<!--
### Synopsis
-->
### 概要
<!--
Upload configuration about the current state, so that 'kubeadm upgrade' can later know how to configure the upgraded cluster.
-->
上传关于当前状态的配置，以便 'kubeadm upgrade' 以后可以知道如何配置升级后的集群。
```
@@ -26,10 +20,6 @@ kubeadm config upload [flags]
### 选项
<!--
<td></td><td style="line-height: 130%; word-wrap: break-word;">help for upload</td>
-->
<table style="width: 100%; table-layout: fixed;">
<colgroup>
<col span="1" style="width: 10px;" />
@@ -54,14 +44,6 @@ kubeadm config upload [flags]
### 从父命令继承的选项
<!--
<td colspan="2">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td>
<td></td><td style="line-height: 130%; word-wrap: break-word;">The KubeConfig file to use when talking to the cluster. If the flag is not set, a set of standard locations are searched for an existing KubeConfig file.</td>
<td></td><td style="line-height: 130%; word-wrap: break-word;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td>
-->
<table style="width: 100%; table-layout: fixed;">
<colgroup>
<col span="1" style="width: 10px;" />
@@ -70,9 +52,11 @@ kubeadm config upload [flags]
<tbody>
<tr>
<!-- td colspan="2">kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td -->
<td colspan="2">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值： "/etc/kubernetes/admin.conf"</td>
</tr>
<tr>
<!-- td></td><td style="line-height: 130%; word-wrap: break-word;">The KubeConfig file to use when talking to the cluster. If the flag is not set, a set of standard locations are searched for an existing KubeConfig file.</td -->
<td></td><td style="line-height: 130%; word-wrap: break-word;">用于和集群通信的 KubeConfig 文件。如果它没有被设置，那么 kubeadm 将会搜索一个已经存在于标准路径的 KubeConfig 文件。</td>
</tr>
@@ -80,12 +64,10 @@ kubeadm config upload [flags]
<td colspan="2">--rootfs string</td>
</tr>
<tr>
<!-- td></td><td style="line-height: 130%; word-wrap: break-word;">[EXPERIMENTAL] The path to the 'real' host root filesystem.</td -->
<td></td><td style="line-height: 130%; word-wrap: break-word;">[实验] 到'真实'主机根文件系统的路径。</td>
</tr>
</tbody>
</table>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_reset_phase_update-cluster-status.md
+6 -9
View File
@@ -2,12 +2,13 @@
<!--
### Synopsis
-->
### 概要
### 概要
<!--
Remove this node from the ClusterStatus object if the node is a control plane node.
-->
如果该节点是控制平面节点，从 ClusterStatus 对象中删除该节点。
```
@@ -17,6 +18,7 @@ kubeadm reset phase update-cluster-status [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -31,9 +33,7 @@ kubeadm reset phase update-cluster-status [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for update-cluster-status
-->
<!-- help for update-cluster-status -->
update-cluster-status 操作的帮助命令
</td>
</tr>
@@ -41,11 +41,10 @@ kubeadm reset phase update-cluster-status [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@@ -60,9 +59,7 @@ kubeadm reset phase update-cluster-status [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 指向 '真实' 宿主机根文件系统的路径。
</td>
</tr>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_token.md
+8 -4
View File
@@ -2,13 +2,13 @@
<!--
### Synopsis
-->
### 概要
<!--
This command manages bootstrap tokens. It is optional and needed only for advanced use cases.
-->
此命令管理引导令牌（bootstrap token）。它是可选的，仅适用于高级用例。
<!--
@@ -16,6 +16,7 @@ In short, bootstrap tokens are used for establishing bidirectional trust between
A bootstrap token can be used when a client (for example a node that is about to join the cluster) needs
to trust the server it is talking to. Then a bootstrap token with the "signing" usage can be used.
-->
简而言之，引导令牌（bootstrap token）用于在客户端和服务器之间建立双向信任。
当客户端（例如，即将加入集群的节点）需要时，可以使用引导令牌相信正在与之通信的服务器。
然后可以使用具有 “签名” 的引导令牌。
@@ -24,6 +25,7 @@ to trust the server it is talking to. Then a bootstrap token with the "signing"
bootstrap tokens can also function as a way to allow short-lived authentication to the API Server
(the token serves as a way for the API Server to trust the client), for example for doing the TLS Bootstrap.
-->
引导令牌还可以作为一种允许对 API 服务器进行短期身份验证的方法（令牌用作 API 服务器信任客户端的方式），例如用于执行 TLS 引导程序。
<!--
@@ -33,7 +35,9 @@ What is a bootstrap token more exactly?
while the latter is the Token Secret and it must be kept private at all circumstances!
- The name of the Secret must be named "bootstrap-token-(token-id)".
-->
引导令牌准确来说是什么？
- 它是位于 kube-system 命名空间中类型为 “bootstrap.kubernetes.io/token” 的一个 Secret。
- 引导令牌的格式必须为 “[a-z0-9]{6}.[a-z0-9]{16}”，前一部分是公共令牌 ID，而后者是令牌秘钥，必须在任何情况下都保密！
- 必须将 Secret 的名称命名为 “bootstrap-token-(token-id)”。
@@ -42,6 +46,7 @@ What is a bootstrap token more exactly?
You can read more about bootstrap tokens here:
/docs/admin/bootstrap-tokens/
-->
您可以在此处阅读有关引导令牌（bootstrap token）的更多信息：
/docs/admin/bootstrap-tokens/
@@ -52,6 +57,7 @@ kubeadm token [flags]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -114,8 +120,6 @@ kubeadm token [flags]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_create.md
+4 -4
View File
@@ -2,10 +2,9 @@
<!--
### Synopsis
-->
### 概要
<!--
This command will create a bootstrap token for you.
You can specify the usages for this token, the "time to live" and an optional human friendly description.
@@ -14,6 +13,7 @@ The [token] is the actual token to write.
This should be a securely generated random token of the form "[a-z0-9]{6}.[a-z0-9]{16}".
If no [token] is given, kubeadm will generate a random token instead.
-->
这个命令将为你创建一个引导令牌。
您可以设置此令牌的用途，"有效时间" 和可选的人性化的描述。
@@ -28,6 +28,7 @@ kubeadm token create [token]
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -139,11 +140,10 @@ kubeadm token create [token]
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_delete.md
+5 -6
View File
@@ -2,20 +2,19 @@
<!--
### Synopsis
-->
### 概要
<!--
This command will delete a list of bootstrap tokens for you.
The [token-value] is the full Token of the form "[a-z0-9]{6}.[a-z0-9]{16}" or the
Token ID of the form "[a-z0-9]{6}" to delete.
-->
这个命令将为你删除指定的引导令牌列表。
[token-value] 是要删除的 "[a-z0-9]{6}.[a-z0-9]{16}" 形式的完整令牌或者是 "[a-z0-9]{6}" 形式的的令牌 ID。
`[token-value]` 是要删除的 "[a-z0-9]{6}.[a-z0-9]{16}" 形式的完整令牌或者是 "[a-z0-9]{6}" 形式的的令牌 ID。
```
kubeadm token delete [token-value] ...
@@ -24,6 +23,7 @@ kubeadm token delete [token-value] ...
<!--
### Options
-->
### 选项
<table style="width: 100%; table-layout: fixed;">
@@ -48,11 +48,10 @@ kubeadm token delete [token-value] ...
</tbody>
</table>
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_generate.md
+3 -10
View File
@@ -2,10 +2,9 @@
<!--
### Synopsis
-->
### 概要
<!--
This command will print out a randomly-generated bootstrap token that can be used with
the "init" and "join" commands.
@@ -19,9 +18,7 @@ generate and print one for you.
-->
此命令将打印一个随机生成的可以被 "init" 和 "join" 命令使用的引导令牌。
您不必使用此命令来生成令牌。你可以自己设定，只要格式符合 "[a-z0-9]{6}.[a-z0-9]{16}"。这个命令提供是为了方便生成规定格式的令牌。
您也可以使用 "kubeadm init" 并且不指定令牌，该命令会生成一个令牌并打印出来。
```
@@ -74,9 +71,7 @@ kubeadm token generate [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Whether to enable dry-run mode or not
-->
<!-- Whether to enable dry-run mode or not -->
是否启用 `dry-run` 运行模式</td>
</tr>
@@ -102,9 +97,7 @@ kubeadm token generate [flags]
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
[实验] 指向 '真实' 宿主机根文件系统的路径。
</td>
</tr>

Some files were not shown because too many files have changed in this diff Show More