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

[zh]Sync kubeadm-7

pull/33621/head
wei.wang 2022-05-12 01:42:09 +08:00
parent 994555c46b
commit cf483c543f
6 changed files with 102 additions and 72 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -87,6 +87,3 @@ kubeadm certs renew etcd-server [flags]
</tbody>
</table>

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

@ -67,6 +67,3 @@ kubeadm config images [flags]
</tbody>
</table>

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

@ -117,6 +117,3 @@ kubeadm upgrade node [flags]
</tbody>
</table>

61
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_certs_renew_etcd-server.md
View File

@ -1,3 +1,18 @@
<!--
The file is auto-generated from the Go source code of the component using a generic
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
<!--
Renew the certificate for serving etcd
-->
续订用于提供 etcd 服务的证书
<!--
### Synopsis
@ -21,7 +36,7 @@ Renewal by default tries to use the certificate authority in the local PKI manag
可以使用 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.
After renewal, in order to make changes effective, is required to restart control-plane components and eventually re-distribute the renewed certificate in case the file is used elsewhere.
-->
续订后，为了使更改生效，需要重新启动控制平面组件，并最终重新分发更新的证书，以防文件在其他地方使用。
@ -54,7 +69,9 @@ kubeadm certs renew etcd-server [flags]
<!--
The path where to save the certificates.
-->
<p>
保存证书的路径。
</p>
</td>
</tr>
@ -66,31 +83,9 @@ The path where to save the certificates.
<!--
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>
</td>
</tr>
@ -102,7 +97,9 @@ Create CSRs instead of generating certificates
<!--
help for etcd-server
-->
<p>
etcd-server 操作的帮助命令
</p>
</td>
</tr>
@ -119,22 +116,16 @@ etcd-server 操作的帮助命令
<!--
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>
</td>
</tr>
<tr>
<td colspan="2">--use-api</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Use the Kubernetes certificate API to renew certificates
-->
使用 Kubernetes 证书 API 续订证书
</td>
</tr>
</tbody>
</table>
@ -142,7 +133,6 @@ Use the Kubernetes certificate API to renew certificates
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@ -160,10 +150,11 @@ Use the Kubernetes certificate API to renew certificates
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<p>
[实验] 到 '真实' 主机根文件系统的路径。
</p>
</td>
</tr>
</tbody>
</table>

22
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images.md
View File

@ -1,3 +1,18 @@
<!--
The file is auto-generated from the Go source code of the component using a generic
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
<!--
Interact with container images used by kubeadm
-->
与 kubeadm 使用的容器镜像交互
<!--
### Synopsis
@ -36,7 +51,9 @@ kubeadm config images [flags]
<!--
help for images
-->
<p>
images 的帮助命令
</p>
</td>
</tr>
@ -47,7 +64,6 @@ images 的帮助命令
<!--
### Options inherited from parent commands
-->
### 从父命令继承的选项
<table style="width: 100%; table-layout: fixed;">
@ -70,7 +86,9 @@ images 的帮助命令
<!--
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 文件。如果它没有被设置，那么 kubeadm 将会搜索一个已经存在于标准路径的 kubeconfig 文件。
</p>
</td>
</tr>
@ -82,7 +100,9 @@ The kubeconfig file to use when talking to the cluster. If the flag is not set,
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<p>
[实验] 到 '真实' 主机根文件系统的路径。
</p>
</td>
</tr>

82
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_node.md
View File

@ -1,3 +1,18 @@
<!--
The file is auto-generated from the Go source code of the component using a generic
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
<!--
Upgrade commands for a node in the cluster
-->
升级集群中某个节点的命令
<!--
### Synopsis
@ -8,7 +23,6 @@
<!--
Upgrade commands for a node in the cluster
-->
升级集群中某个节点的命令
<!--
@ -49,14 +63,16 @@ kubeadm upgrade node [flags]
<tbody>
<tr>
<td colspan="2">--certificate-renewal</td>
<td colspan="2">--certificate-renewal&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<!--Default-->默认值: true</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Perform the renewal of certificates used by component changed during upgrades.
-->
<p>
对升级期间变化的组件所使用的证书执行更新。
</p>
</td>
</tr>
@ -69,7 +85,9 @@ Perform the renewal of certificates used by component changed during upgrades.
<!--
Do not change any state, just output the actions that would be performed.
-->
<p>
不更改任何状态，只输出将要执行的操作。
</p>
</td>
</tr>
@ -84,23 +102,9 @@ Do not change any state, just output the actions that would be performed.
<!--
Perform the upgrade of etcd.
-->
<p>
执行 etcd 的升级。
</td>
</tr>
<tr>
<td colspan="2">--experimental-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 支持的补丁格式匹配。
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</p>
</td>
</tr>
@ -112,10 +116,23 @@ Path to a directory that contains files named "target[suffix][+patchtype].extens
<!--
help for node
-->
<p>
node 操作的帮助命令
</p>
</td>
</tr>
<tr>
<td colspan="2">--ignore-preflight-errors strings</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>
<!-- A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedUser,Swap'. Value 'all' ignores errors from all checks. -->
其错误将显示为警告的检查列表。示例：'IsPrivilegedUser,Swap'。 值 'all' 忽略所有检查中的错误。
</p></td>
</tr>
<tr>
<!--
<td colspan="2">--kubeconfig string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "/etc/kubernetes/admin.conf"</td>
@ -127,31 +144,41 @@ node 操作的帮助命令
<!--
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>
</td>
</tr>
<tr>
<td colspan="2">--kubelet-version string</td>
<td colspan="2">--patches string</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The *desired* version for the kubelet config after the upgrade. If not specified, the KubernetesVersion from the kubeadm-config ConfigMap will be used
-->
升级后 *期望的* kubelet 配置版本。如未指定，将使用 kubeadm-config ConfigMap 中的 KubernetesVersion
</td>
<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>
<!-- Path to a directory that contains files named &quot;target[suffix][+patchtype].extension&quot;. For example, &quot;kube-apiserver0+merge.yaml&quot; or just &quot;etcd.json&quot;. &quot;target&quot; can be one of &quot;kube-apiserver&quot;, &quot;kube-controller-manager&quot;, &quot;kube-scheduler&quot;, &quot;etcd&quot;. &quot;patchtype&quot; can be one of &quot;strategic&quot;, &quot;merge&quot; or &quot;json&quot; and they match the patch formats supported by kubectl. The default &quot;patchtype&quot; is &quot;strategic&quot;. &quot;extension&quot; must be either &quot;json&quot; or &quot;yaml&quot;. &quot;suffix&quot; is an optional string that can be used to determine which patches are applied first alpha-numerically. -->
包含名为 &quot;target[suffix][+patchtype].extension&quot; 的文件的目录的路径。
例如，&quot;kube-apiserver0+merge.yaml&quot;或仅仅是 &quot;etcd.json&quot;。
&quot;target&quot; 可以是 &quot;kube-apiserver&quot;、&quot;kube-controller-manager&quot;、&quot;kube-scheduler&quot;、&quot;etcd&quot; 之一。
&quot;patchtype&quot; 可以是 &quot;strategic&quot;、&quot;merge&quot; 或者 &quot;json&quot; 之一，
并且它们与 kubectl 支持的补丁格式相同。
默认的 &quot;patchtype&quot; 是 &quot;strategic&quot;。
&quot;extension&quot; 必须是&quot;json&quot; 或&quot;yaml&quot;。
&quot;suffix&quot; 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</p></td>
</tr>
</tr>
<tr>
<td colspan="2">--skip-phases stringSlice</td>
<td colspan="2">--skip-phases strings</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
List of phases to be skipped
-->
<p>
要跳过的阶段的列表
</p>
</td>
</tr>
@ -179,10 +206,11 @@ List of phases to be skipped
<!--
[EXPERIMENTAL] The path to the 'real' host root filesystem.
-->
<p>
[实验] 指向 '真实' 宿主机根文件系统的路径。
</p>
</td>
</tr>
</tbody>
</table>