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

[zh] sync v1.24 kubeadm-11

Browse Source
This commit is contained in:
huangminjie
2022-05-11 21:39:02 +08:00
parent 8a530c3a08
commit 1992c0881e
4 changed files with 167 additions and 82 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_certs_check-expiration.md
+57 -9
View File
@@ -1,3 +1,19 @@
<!--
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.
-->
<!--
Check certificates expiration for a Kubernetes cluster
-->
为一个 Kubernetes 集群检查证书的到期时间
<!--
### Synopsis
-->
@@ -31,26 +47,54 @@ kubeadm certs check-expiration [flags]
<td colspan="2">--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 the certificates</td>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
<p>The path where to save the certificates</p>
-->
<td></td><td style="line-height: 130%; word-wrap: break-word;">保存证书的路径</td>
<p>保存证书的路径</p>
</td>
</tr>
<tr>
<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;">kubeadm 配置文件的路径</td>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
<p>Path to a kubeadm configuration file.</p>
-->
<p>kubeadm 配置文件的路径</p>
</td>
</tr>
<tr>
<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;">check-expiration 的帮助命令</td>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
<p>help for check-expiration</p>
-->
<p>check-expiration 的帮助命令</p>
</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;默认为: "/etc/kubernetes/admin.conf"
</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
<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>
-->
<p>在和集群连接时使用该 kubeconfig 文件。
如果该标志没有设置，那么将会在一些标准的位置去搜索存在的 kubeconfig 文件。</p>
</td>
</tr>
</tbody>
@@ -72,8 +116,12 @@ kubeadm 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;">[实验] 到'真实'主机根文件系统的路径。</td>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
<p>[EXPERIMENTAL] The path to the 'real' host root filesystem.</p>
-->
<p>[实验] 到'真实'主机根文件系统的路径。</p>
</td>
</tr>
</tbody>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_certs_renew_admin.conf.md
+26 -33
View File
@@ -1,3 +1,18 @@
<!--
The file is auto-generated from the Go source code of the component using a generic
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
<!--
Renew the certificate embedded in the kubeconfig file for the admin to use and for kubeadm itself
-->
续订 kubeconfig 文件中嵌入的证书，供管理员 和 kubeadm 自身使用。
<!--
### Synopsis
@@ -51,9 +66,9 @@ kubeadm certs renew admin.conf [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>
@@ -62,30 +77,8 @@ The path where to save the certificates.
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- Path to a kubeadm configuration file. -->
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>Path to a kubeadm configuration file.</p> -->
<p>kubeadm 配置文件的路径。</p>
</td>
</tr>
@@ -94,8 +87,8 @@ Create CSRs instead of generating certificates
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- help for admin.conf -->
admin.conf 子操作的帮助命令
<!-- <p>help for admin.conf</p> -->
<p>admin.conf 子操作的帮助命令</p>
</td>
</tr>
@@ -104,9 +97,9 @@ admin.conf 子操作的帮助命令
</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. -->
与集群通信时使用的 kubeconfig 文件。
如果未设置该参数，则可以在一组标准位置中搜索现有的 kubeconfig 文件。
<!-- <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> -->
<p>与集群通信时使用的 kubeconfig 文件。
如果未设置该参数，则可以在一组标准位置中搜索现有的 kubeconfig 文件。</p>
</td>
</tr>
@@ -143,9 +136,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>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-healthcheck-client.md
+28 -15
View File
@@ -1,3 +1,19 @@
<!--
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 liveness probes to healthcheck etcd
-->
生成用于 etcd 健康检查的活跃性探针的证书
<!--
### Synopsis
@@ -6,21 +22,18 @@
### 概要
<!--
Generate the certificate for liveness probes to healthcheck etcd, and save them into etcd/healthcheck-client.cert and etcd/healthcheck-client.key files.
Generate the certificate for liveness probes to healthcheck etcd, and save them into etcd/healthcheck-client.crt and etcd/healthcheck-client.key files
-->
生成用于 etcd 健康检查的活跃性探针的证书，并将其保存到 healthcheck-client.cert 和 etcd/healthcheck-client.key 文件中。
生成用于 etcd 健康检查的活跃性探针的证书，并将其保存到 etcd/healthcheck-client.crt 和 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 功能。
```
@@ -51,9 +64,9 @@ kubeadm init phase certs etcd-healthcheck-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>
@@ -63,9 +76,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>
@@ -75,9 +88,9 @@ kubeadm 配置文件的路径。
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for etcd-healthcheck-client
<p>help for etcd-healthcheck-client</p>
-->
etcd-healthcheck-client 操作的帮助命令
<p>etcd-healthcheck-client 操作的帮助命令</p>
</td>
</tr>
@@ -92,9 +105,9 @@ etcd-healthcheck-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>
@@ -120,9 +133,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>
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_scheduler.md
+56 -25
View File
@@ -1,3 +1,18 @@
<!--
The file is auto-generated from the Go source code of the component using a generic
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
<!--
Generates the kube-scheduler static Pod manifest
-->
生成 kube-scheduler 静态 Pod 清单
<!--
### Synopsis
@@ -36,9 +51,9 @@ kubeadm init phase control-plane scheduler [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>
@@ -48,25 +63,21 @@ 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>
<tr>
<td colspan="2">--experimental-patches string</td>
<td colspan="2">--dry-run</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "patchtype" can be one of "strategic", "merge" or "json" and they match the patch formats supported by kubectl. The default "patchtype" is "strategic". "extension" must be either "json" or "yaml". "suffix" is an optional string that can be used to determine which patches are applied first alpha-numerically.-->
包含名为 "target[suffix][+patchtype].extension" 的文件的目录。
例如，"kube-apiserver0+merge.yaml" 或者 "etcd.json"。
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，分别与 kubectl
所支持的 patch 格式相匹配。默认的 "patchtype" 是 "strategic"。
"extension" 必须是 "json" 或 "yaml"。
"suffix" 是一个可选的字符串，用来确定按字母顺序排序时首先应用哪些 patch。
<!--
<p>Don't apply any changes; just output what would be done.</p>
-->
<p>不应用任何变更；仅仅输出将会变更的内容</p>
</td>
</tr>
@@ -76,9 +87,9 @@ kubeadm 配置文件的路径。
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
help for scheduler
<p>help for scheduler</p>
-->
scheduler 操作的帮助命令
<p>scheduler 操作的帮助命令</p>
</td>
</tr>
@@ -93,9 +104,9 @@ scheduler 操作的帮助命令
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Choose a container registry to pull control plane images from
<p>Choose a container registry to pull control plane images from</p>
-->
选择要从中拉取控制平面镜像的容器仓库
<p>选择要从中拉取控制平面镜像的容器仓库</p>
</td>
</tr>
@@ -110,22 +121,42 @@ Choose a container registry to pull control plane images from
<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>
<tr>
<td colspan="2">--scheduler-extra-args mapStringString</td>
<td colspan="2">--patches string</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "patchtype" can be one of "strategic", "merge" or "json" and they match the patch formats supported by kubectl. The default "patchtype" is "strategic". "extension" must be either "json" or "yaml". "suffix" is an optional string that can be used to determine which patches are applied first alpha-numerically.-->
包含名为 "target[suffix][+patchtype].extension" 的文件的目录。
例如，"kube-apiserver0+merge.yaml" 或者 "etcd.json"。
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，分别与 kubectl
所支持的 patch 格式相匹配。默认的 "patchtype" 是 "strategic"。
"extension" 必须是 "json" 或 "yaml"。
"suffix" 是一个可选的字符串，用来确定按字母顺序排序时首先应用哪些 patch。
</td>
</tr>
<tr>
<td colspan="2">
<!--
--scheduler-extra-args &lt;comma-separated 'key=value' pairs&gt;
-->
--scheduler-extra-args &lt;逗号分隔的 'key=value' 键值对&gt;
</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
A set of extra flags to pass to the Scheduler or override default ones in form of &lt;flagname&gt;=&lt;value&gt;
<p>A set of extra flags to pass to the Scheduler or override default ones in form of &lt;flagname&gt;=&lt;value&gt;</p>
-->
一组 &lt;flagname&gt;=&lt;value&gt; 形式的额外参数，用来传递给调度器
或者覆盖其默认参数配置
<p>一组 &lt;flagname&gt;=&lt;value&gt; 形式的额外参数，用来传递给调度器
或者覆盖其默认参数配置</p>
</td>
</tr>
@@ -150,9 +181,9 @@ A set of extra flags to pass to the Scheduler or override default ones in form o
<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>