[zh] sync v1.24 kubeadm-21
parent
9c6b1910e6
commit
3acf1cddcd
|
@ -1,3 +1,18 @@
|
|||
<!--
|
||||
The file is auto-generated from the Go source code of the component using a generic
|
||||
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
|
||||
to generate the reference documentation, please read
|
||||
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
|
||||
To update the reference conent, please follow the
|
||||
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
|
||||
guide. You can file document formatting bugs against the
|
||||
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Renew the certificate for the front proxy client
|
||||
-->
|
||||
为前端代理客户端续订证书。
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
|
@ -48,9 +63,9 @@ kubeadm certs renew front-proxy-client [flags]
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
The path where to save the certificates
|
||||
<p>The path where to save the certificates</p>
|
||||
-->
|
||||
存储证书的路径。
|
||||
<p>存储证书的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -60,33 +75,9 @@ The path where to save the certificates
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Path to a kubeadm configuration file.
|
||||
<p>Path to a kubeadm configuration file.</p>
|
||||
-->
|
||||
kubeadm 配置文件的路径。
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--csr-dir string</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
The path to output the CSRs and private keys to
|
||||
-->
|
||||
输出 CSR 和私钥的路径
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--csr-only</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Create CSRs instead of generating certificates
|
||||
-->
|
||||
创建 CSR 而不是生成证书
|
||||
<p>kubeadm 配置文件的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -96,9 +87,9 @@ Create CSRs instead of generating certificates
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
help for front-proxy-client
|
||||
<p>help for front-proxy-client</p>
|
||||
-->
|
||||
front-proxy-client 操作的帮助命令
|
||||
<p>front-proxy-client 操作的帮助命令</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -113,10 +104,10 @@ front-proxy-client 操作的帮助命令
|
|||
<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.
|
||||
<p>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.</p>
|
||||
-->
|
||||
与集群通信时使用的 kubeconfig 文件。
|
||||
如果未设置该参数,则可以在一组标准位置中搜索现有的 kubeconfig 文件。
|
||||
<p>与集群通信时使用的 kubeconfig 文件。
|
||||
如果未设置该参数,则可以在一组标准位置中搜索现有的 kubeconfig 文件。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -153,9 +144,9 @@ Use the Kubernetes certificate API to renew certificates
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
[EXPERIMENTAL] The path to the 'real' host root filesystem.
|
||||
<p>[EXPERIMENTAL] The path to the 'real' host root filesystem.</p>
|
||||
-->
|
||||
[实验] 到 '真实' 主机根文件系统的路径。
|
||||
<p>[实验] 到 '真实' 主机根文件系统的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
|
@ -1,3 +1,18 @@
|
|||
<!--
|
||||
The file is auto-generated from the Go source code of the component using a generic
|
||||
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
|
||||
to generate the reference documentation, please read
|
||||
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
|
||||
To update the reference conent, please follow the
|
||||
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
|
||||
guide. You can file document formatting bugs against the
|
||||
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Use this command to invoke single phase of the init workflow
|
||||
-->
|
||||
使用此命令可以调用 init 工作流程的单个阶段
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
|
@ -29,8 +44,10 @@ 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 -->
|
||||
phase 操作的帮助命令
|
||||
<!--
|
||||
<p>help for phase</p>
|
||||
-->
|
||||
<p>phase 操作的帮助命令</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -56,9 +73,9 @@ phase 操作的帮助命令
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
[EXPERIMENTAL] The path to the 'real' host root filesystem.
|
||||
<p>[EXPERIMENTAL] The path to the 'real' host root filesystem.</p>
|
||||
-->
|
||||
[实验] 到 '真实' 主机根文件系统的路径。
|
||||
<p>[实验] 到 '真实' 主机根文件系统的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
|
@ -1,3 +1,18 @@
|
|||
<!--
|
||||
The file is auto-generated from the Go source code of the component using a generic
|
||||
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
|
||||
to generate the reference documentation, please read
|
||||
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
|
||||
To update the reference conent, please follow the
|
||||
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
|
||||
guide. You can file document formatting bugs against the
|
||||
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Generate the certificate the apiserver uses to access etcd
|
||||
-->
|
||||
生成 apiserver 用来访问 etcd 的证书
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
|
@ -6,10 +21,10 @@
|
|||
### 概要
|
||||
|
||||
<!--
|
||||
Generate the certificate the apiserver uses to access etcd, and save them into apiserver-etcd-client.cert and apiserver-etcd-client.key files.
|
||||
Generate the certificate the apiserver uses to access etcd, and save them into apiserver-etcd-client.crt and apiserver-etcd-client.key files.
|
||||
-->
|
||||
|
||||
生成 apiserver 用于访问 etcd 的证书,并将其保存到 apiserver-etcd-client.cert 和 apiserver-etcd-client.key 文件中。
|
||||
生成 apiserver 用于访问 etcd 的证书,并将其保存到 apiserver-etcd-client.crt 和 apiserver-etcd-client.key 文件中。
|
||||
|
||||
<!--
|
||||
If both files already exist, kubeadm skips the generation step and existing files will be used.
|
||||
|
@ -50,8 +65,10 @@ 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. -->
|
||||
证书的存储路径。
|
||||
<!--
|
||||
<p>The path where to save and store the certificates.</p>
|
||||
-->
|
||||
<p>证书的存储路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -60,8 +77,10 @@ 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. -->
|
||||
kubeadm 配置文件的路径。
|
||||
<!--
|
||||
<p>Path to a kubeadm configuration file.</p>
|
||||
-->
|
||||
<p>kubeadm 配置文件的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -70,8 +89,10 @@ kubeadm 配置文件的路径。
|
|||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- help for apiserver-etcd-client -->
|
||||
apiserver-etcd-client 操作的帮助命令
|
||||
<!--
|
||||
<p>help for apiserver-etcd-client</p>
|
||||
-->
|
||||
<p>apiserver-etcd-client 操作的帮助命令</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -84,9 +105,9 @@ apiserver-etcd-client 操作的帮助命令
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Choose a specific Kubernetes version for the control plane.
|
||||
<p>Choose a specific Kubernetes version for the control plane.</p>
|
||||
-->
|
||||
为控制平面指定特定的 Kubernetes 版本。
|
||||
<p>为控制平面指定特定的 Kubernetes 版本。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -111,8 +132,10 @@ Choose a specific Kubernetes version for the control plane.
|
|||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
|
||||
[实验] 到 '真实' 主机根文件系统的路径。
|
||||
<!--
|
||||
<p>[EXPERIMENTAL] The path to the 'real' host root filesystem.</p>
|
||||
-->
|
||||
<p>[实验] 到 '真实' 主机根文件系统的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
|
@ -1,3 +1,18 @@
|
|||
<!--
|
||||
The file is auto-generated from the Go source code of the component using a generic
|
||||
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
|
||||
to generate the reference documentation, please read
|
||||
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
|
||||
To update the reference conent, please follow the
|
||||
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
|
||||
guide. You can file document formatting bugs against the
|
||||
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Generate the certificate for the front proxy client
|
||||
-->
|
||||
为前端代理客户端生成证书
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
|
@ -6,12 +21,12 @@
|
|||
### 概要
|
||||
|
||||
<!--
|
||||
Generate the certificate for the front proxy client, and save them into front-proxy-client.cert and front-proxy-client.key files.
|
||||
Generate the certificate for the front proxy client, and save them into front-proxy-client.crt 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 文件中。
|
||||
为前端代理客户端生成证书,并将其保存到 front-proxy-client.crt 和 front-proxy-client.key 文件中。
|
||||
如果两个文件都已存在,kubeadm 将跳过生成步骤并将使用现有文件。
|
||||
Alpha 免责声明:此命令目前是 alpha 阶段。
|
||||
|
||||
|
@ -42,9 +57,9 @@ kubeadm init phase certs front-proxy-client [flags]
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
The path where to save and store the certificates.
|
||||
<p>The path where to save and store the certificates.</p>
|
||||
-->
|
||||
存储证书的路径。
|
||||
<p>存储证书的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -54,9 +69,9 @@ The path where to save and store the certificates.
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Path to a kubeadm configuration file.
|
||||
<p>Path to a kubeadm configuration file.</p>
|
||||
-->
|
||||
kubeadm 配置文件的路径。
|
||||
<p>kubeadm 配置文件的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -66,9 +81,9 @@ kubeadm 配置文件的路径。
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
help for front-proxy-client
|
||||
<p>help for front-proxy-client</p>
|
||||
-->
|
||||
front-proxy-client 操作的帮助命令
|
||||
<p>front-proxy-client 操作的帮助命令</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -83,9 +98,9 @@ front-proxy-client 操作的帮助命令
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Choose a specific Kubernetes version for the control plane.
|
||||
<p>Choose a specific Kubernetes version for the control plane.</p>
|
||||
-->
|
||||
为控制平面选择特定的 Kubernetes 版本。
|
||||
<p>为控制平面选择特定的 Kubernetes 版本。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
@ -111,9 +126,9 @@ Choose a specific Kubernetes version for the control plane.
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
[EXPERIMENTAL] The path to the 'real' host root filesystem.
|
||||
<p>[EXPERIMENTAL] The path to the 'real' host root filesystem.</p>
|
||||
-->
|
||||
[实验] 到 '真实' 主机根文件系统的路径。
|
||||
<p>[实验] 到 '真实' 主机根文件系统的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
Loading…
Reference in New Issue