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

sync changes in docs/reference/setup-tools/kubeadm/generated/ directory

pull/25267/head
Hao Yuan 2020-11-27 14:36:48 +08:00
parent c589c391eb
commit ecaa42b7b9
22 changed files with 210 additions and 300 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_config_images_list.md
View File

@ -28,6 +28,37 @@ kubeadm config images list [flags]
</colgroup> </colgroup>
<tbody> <tbody>
<tr>
<td colspan="2">
<!-- --allow-missing-template-keys&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true -->
--allow-missing-template-keys&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值：true
</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.
-->
如果设置为 true，则在模板中缺少字段或哈希表的键时忽略模板中的任何错误。
仅适用于 golang 和 jsonpath 输出格式。
</td>
</tr>
<tr>
<td colspan="2">
<!-- -o, --experimental-output string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "text" -->
-o, --experimental-output string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值："text"
</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Output format. One of: text|json|yaml|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
-->
输出格式：text|json|yaml|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file 其中之一
</td>
</tr>
<tr> <tr>
<td colspan="2">--config string</td> <td colspan="2">--config string</td>
</tr> </tr>
@ -48,7 +79,10 @@ kubeadm 配置文件的路径。
<!-- <!--
A set of key=value pairs that describe feature gates for various features. Options are:<br/>IPv6DualStack=true|false (ALPHA - default=false) A set of key=value pairs that describe feature gates for various features. Options are:<br/>IPv6DualStack=true|false (ALPHA - default=false)
--> -->
一组键值对（key=value），用于描述各种特征。选项有：<br/>Auditing=true|false (ALPHA - 默认值=false)<br/>CoreDNS=true|false (默认值=true)<br/>DynamicKubeletConfig=true|false (BETA - 默认值=false) 一组键值对（key=value），用于描述各种特征。选项是：
<br/>Auditing=true|false (ALPHA - 默认=false)
<br/>CoreDNS=true|false (默认=true)
<br/>DynamicKubeletConfig=true|false (BETA - 默认=false)
</td> </td>
</tr> </tr>
@ -64,6 +98,19 @@ list 操作的帮助命令
</td> </td>
</tr> </tr>
<tr>
<td colspan="2">
<!-- --image-repository string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "k8s.gcr.io" -->
--image-repository string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值："k8s.gcr.io"
</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- Choose a container registry to pull control plane images from -->
选择要从中拉取控制平面镜像的容器仓库
</td>
</tr>
<tr> <tr>
<td colspan="2"> <td colspan="2">
<!-- <!--

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

@ -18,40 +18,42 @@ The "init" command executes the following phases:
"init" 命令执行以下阶段： "init" 命令执行以下阶段：
``` ```
preflight Run pre-flight checks preflight Run pre-flight checks
kubelet-start Write kubelet settings and (re)start the kubelet certs Certificate generation
certs Certificate generation /ca Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components
/ca Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components /apiserver Generate the certificate for serving the Kubernetes API
/apiserver Generate the certificate for serving the Kubernetes API /apiserver-kubelet-client Generate the certificate for the API server to connect to kubelet
/apiserver-kubelet-client Generate the certificate for the API server to connect to kubelet /front-proxy-ca Generate the self-signed CA to provision identities for front proxy
/front-proxy-ca Generate the self-signed CA to provision identities for front proxy /front-proxy-client Generate the certificate for the front proxy client
/front-proxy-client Generate the certificate for the front proxy client /etcd-ca Generate the self-signed CA to provision identities for etcd
/etcd-ca Generate the self-signed CA to provision identities for etcd /etcd-server Generate the certificate for serving etcd
/etcd-server Generate the certificate for serving etcd /etcd-peer Generate the certificate for etcd nodes to communicate with each other
/etcd-peer Generate the certificate for etcd nodes to communicate with each other /etcd-healthcheck-client Generate the certificate for liveness probes to healthcheck etcd
/etcd-healthcheck-client Generate the certificate for liveness probes to healthcheck etcd /apiserver-etcd-client Generate the certificate the apiserver uses to access etcd
/apiserver-etcd-client Generate the certificate the apiserver uses to access etcd /sa Generate a private key for signing service account tokens along with its public key
/sa Generate a private key for signing service account tokens along with its public key kubeconfig Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file
kubeconfig Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file /admin Generate a kubeconfig file for the admin to use and for kubeadm itself
/admin Generate a kubeconfig file for the admin to use and for kubeadm itself /kubelet Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes
/kubelet Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes /controller-manager Generate a kubeconfig file for the controller manager to use
/controller-manager Generate a kubeconfig file for the controller manager to use /scheduler Generate a kubeconfig file for the scheduler to use
/scheduler Generate a kubeconfig file for the scheduler to use kubelet-start Write kubelet settings and (re)start the kubelet
control-plane Generate all static Pod manifest files necessary to establish the control plane control-plane Generate all static Pod manifest files necessary to establish the control plane
/apiserver Generates the kube-apiserver static Pod manifest /apiserver Generates the kube-apiserver static Pod manifest
/controller-manager Generates the kube-controller-manager static Pod manifest /controller-manager Generates the kube-controller-manager static Pod manifest
/scheduler Generates the kube-scheduler static Pod manifest /scheduler Generates the kube-scheduler static Pod manifest
etcd Generate static Pod manifest file for local etcd etcd Generate static Pod manifest file for local etcd
/local Generate the static Pod manifest file for a local, single-node local etcd instance /local Generate the static Pod manifest file for a local, single-node local etcd instance
upload-config Upload the kubeadm and kubelet configuration to a ConfigMap upload-config Upload the kubeadm and kubelet configuration to a ConfigMap
/kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap /kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap
/kubelet Upload the kubelet component config to a ConfigMap /kubelet Upload the kubelet component config to a ConfigMap
upload-certs Upload certificates to kubeadm-certs upload-certs Upload certificates to kubeadm-certs
mark-control-plane Mark a node as a control-plane mark-control-plane Mark a node as a control-plane
bootstrap-token Generates bootstrap tokens used to join a node to a cluster bootstrap-token Generates bootstrap tokens used to join a node to a cluster
addon Install required addons for passing Conformance tests kubelet-finalize Updates settings relevant to the kubelet after TLS bootstrap
/coredns Install the CoreDNS addon to a Kubernetes cluster /experimental-cert-rotation Enable kubelet client certificate rotation
/kube-proxy Install the kube-proxy addon to a Kubernetes cluster addon Install required addons for passing Conformance tests
/coredns Install the CoreDNS addon to a Kubernetes cluster
/kube-proxy Install the kube-proxy addon to a Kubernetes cluster
``` ```
``` ```
@ -190,14 +192,18 @@ Don't apply any changes; just output what would be done.
</tr> </tr>
<tr> <tr>
<td colspan="2">-k, --experimental-kustomize string</td> <td colspan="2">--experimental-patches string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- <!--
The path where kustomize patches for static pod manifests are stored. 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.
--> -->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。 包含名为 "target[suffix][+patchtype].extension" 的文件的目录路径。
例如，"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</td> </td>
</tr> </tr>

21
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver-etcd-client.md
View File

@ -65,27 +65,6 @@ kubeadm 配置文件的路径。
</td> </td>
</tr> </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>
</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 而不是生成证书
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

24
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver-kubelet-client.md
View File

@ -69,30 +69,6 @@ kubeadm 配置文件路径。
</td> </td>
</tr> </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 而不是生成证书
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

24
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_apiserver.md
View File

@ -111,30 +111,6 @@ Specify a stable IP address or DNS name for the control plane.
</td> </td>
</tr> </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 而不是生成证书
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

21
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-healthcheck-client.md
View File

@ -69,27 +69,6 @@ kubeadm 配置文件的路径。
</td> </td>
</tr> </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;">
创建 CSR 而不是生成证书
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

20
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-peer.md
View File

@ -71,26 +71,6 @@ kubeadm 配置文件的路径。
</td> </td>
</tr> </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 而不是生成证书
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

24
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_etcd-server.md
View File

@ -70,30 +70,6 @@ kubeadm 配置文件的路径。
</td> </td>
</tr> </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 而不是生成证书
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

24
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_front-proxy-client.md
View File

@ -60,30 +60,6 @@ kubeadm 配置文件的路径。
</td> </td>
</tr> </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 而不是生成证书
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

18
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_all.md
View File

@ -141,27 +141,17 @@ A set of extra flags to pass to the Controller Manager or override default ones
</td> </td>
</tr> </tr>
<tr>
<td colspan="2">-k, --experimental-kustomize string</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path where kustomize patches for static pod manifests are stored.
-->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。
</td>
</tr>
<tr> <tr>
<td colspan="2">--feature-gates string</td> <td colspan="2">--feature-gates string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- <!--
A set of key=value pairs that describe feature gates for various features. Options are:<br/>IPv6DualStack=true|false (ALPHA - default=false) A set of key=value pairs that describe feature gates for various features. Options are:<br/>IPv6DualStack=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)
--> -->
一组用来描述各种功能特性的键值（key=value）对。选项是：<br/>IPv6DualStack=true|false (ALPHA - default=false) 一组用来描述各种功能特性的键值（key=value）对。选项是：
<br/>IPv6DualStack=true|false (ALPHA - 默认=false)
<br/>PublicKeysECDSA=true|false (ALPHA - 默认=false)
</td> </td>
</tr> </tr>

18
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_apiserver.md
View File

@ -109,27 +109,17 @@ Specify a stable IP address or DNS name for the control plane.
</td> </td>
</tr> </tr>
<tr>
<td colspan="2">-k, --experimental-kustomize string</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path where kustomize patches for static pod manifests are stored.
-->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。
</td>
</tr>
<tr> <tr>
<td colspan="2">--feature-gates string</td> <td colspan="2">--feature-gates string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- <!--
A set of key=value pairs that describe feature gates for various features. Options are:<br/>IPv6DualStack=true|false (ALPHA - default=false) A set of key=value pairs that describe feature gates for various features. Options are:<br/>IPv6DualStack=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)
--> -->
一组键值对，用于描述各种特征的特征事项。选项是：<br/>IPv6DualStack=true|false (ALPHA - default=false) 一组键值对，用于描述各种特征的特征事项。选项是：
<br/>IPv6DualStack=true|false (ALPHA - 默认=false)
<br/>PublicKeysECDSA=true|false (ALPHA - 默认=false)
</td> </td>
</tr> </tr>

12
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_controller-manager.md
View File

@ -69,18 +69,6 @@ A set of extra flags to pass to the Controller Manager or override default ones
</td> </td>
</tr> </tr>
<tr>
<td colspan="2">-k, --experimental-kustomize string</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path where kustomize patches for static pod manifests are stored.
-->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

12
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_scheduler.md
View File

@ -57,18 +57,6 @@ kubeadm 配置文件的路径。
</td> </td>
</tr> </tr>
<tr>
<td colspan="2">-k, --experimental-kustomize string</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The path where kustomize patches for static pod manifests are stored.
-->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

12
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_etcd_local.md
View File

@ -75,12 +75,18 @@ kubeadm 配置文件的路径。
</tr> </tr>
<tr> <tr>
<td colspan="2">-k, --experimental-kustomize string</td> <td colspan="2">--experimental-patches string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- The path where kustomize patches for static pod manifests are stored. --> <!--
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。 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" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</td> </td>
</tr> </tr>

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

@ -7,8 +7,8 @@
<!-- <!--
When joining a kubeadm initialized cluster, we need to establish When joining a kubeadm initialized cluster, we need to establish
bidirectional trust. This is split into discovery (having the Node bidirectional trust. This is split into discovery (having the Node
trust the Kubernetes Control Plane) and TLS bootstrap (having the Kubernetes trust the Kubernetes Control Plane) and TLS bootstrap (having the
Control Plane trust the Node). Kubernetes Control Plane trust the Node).
--> -->
当节点加入 kubeadm 初始化的集群时，我们需要建立双向信任。 当节点加入 kubeadm 初始化的集群时，我们需要建立双向信任。
@ -21,7 +21,7 @@ provide a file - a subset of the standard kubeconfig file. This file
can be a local file or downloaded via an HTTPS URL. The forms are can be a local file or downloaded via an HTTPS URL. The forms are
kubeadm join --discovery-token abcdef.1234567890abcdef 1.2.3.4:6443, kubeadm join --discovery-token abcdef.1234567890abcdef 1.2.3.4:6443,
kubeadm join --discovery-file path/to/file.conf, or kubeadm join kubeadm join --discovery-file path/to/file.conf, or kubeadm join
--discovery-file `https://url/file.conf`. Only one form can be used. If --discovery-file https://url/file.conf. Only one form can be used. If
the discovery information is loaded from a URL, HTTPS must be used. 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 Also, in that case the host installed CA bundle is used to verify
the connection. the connection.
@ -39,7 +39,9 @@ the connection.
<!-- <!--
If you use a shared token for discovery, you should also pass the If you use a shared token for discovery, you should also pass the
--discovery-token-ca-cert-hash flag to validate the public key of the --discovery-token-ca-cert-hash flag to validate the public key of the
root certificate authority (CA) presented by the Kubernetes Control Plane. The value of this flag is specified as "&lt;hash-type&gt;:&lt;hex-encoded-value&gt;",where the supported hash type is "sha256". The hash is calculated over root certificate authority (CA) presented by the Kubernetes Control Plane.
The value of this flag is specified as "&lt;hash-type&gt;:&lt;hex-encoded-value&gt;",
where the supported hash type is "sha256". The hash is calculated over
the bytes of the Subject Public Key Info (SPKI) object (as in RFC7469). the bytes of the Subject Public Key Info (SPKI) object (as in RFC7469).
This value is available in the output of "kubeadm init" or can be This value is available in the output of "kubeadm init" or can be
calculated using standard tools. The --discovery-token-ca-cert-hash flag calculated using standard tools. The --discovery-token-ca-cert-hash flag
@ -241,14 +243,18 @@ For token-based discovery, allow joining without --discovery-token-ca-cert-hash
</tr> </tr>
<tr> <tr>
<td colspan="2">-k, --experimental-kustomize string</td> <td colspan="2">--experimental-patches string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- <!--
The path where kustomize patches for static pod manifests are stored. 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.
--> -->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。 包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
例如，"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</td> </td>
</tr> </tr>

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

@ -65,14 +65,18 @@ Create a new control plane instance on this node
</tr> </tr>
<tr> <tr>
<td colspan="2">-k, --experimental-kustomize string</td> <td colspan="2">--experimental-patches string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- <!--
The path where kustomize patches for static pod manifests are stored. 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.
--> -->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。 包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
例如，"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
"patchtype" 可以是"strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</td> </td>
</tr> </tr>

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

@ -142,14 +142,18 @@ For token-based discovery, allow joining without --discovery-token-ca-cert-hash
</tr> </tr>
<tr> <tr>
<td colspan="2">-k, --experimental-kustomize string</td> <td colspan="2">--experimental-patches string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- <!--
The path where kustomize patches for static pod manifests are stored. 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.
--> -->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。 包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
例如，"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</td> </td>
</tr> </tr>

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

@ -82,14 +82,18 @@ Create a new control plane instance on this node
</tr> </tr>
<tr> <tr>
<td colspan="2">-k, --experimental-kustomize string</td> <td colspan="2">--experimental-patches string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- <!--
The path where kustomize patches for static pod manifests are stored. 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.
--> -->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。 包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
例如，"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</td> </td>
</tr> </tr>

31
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_token_list.md
View File

@ -27,6 +27,37 @@ kubeadm token list [flags]
</colgroup> </colgroup>
<tbody> <tbody>
<tr>
<td colspan="2">
<!-- --allow-missing-template-keys&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: true -->
--allow-missing-template-keys&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值：true
</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.
-->
如果设置为 true，则在模板中缺少字段或哈希表的键时忽略模板中的任何错误。
仅适用于 golang 和 jsonpath 输出格式。
</td>
</tr>
<tr>
<td colspan="2">
<!-- -o, --experimental-output string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: "text" -->
-o, --experimental-output string&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值："text"
</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Output format. One of: text|json|yaml|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
-->
输出格式：text|json|yaml|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file 其中之一
</td>
</tr>
<tr> <tr>
<td colspan="2">-h, --help</td> <td colspan="2">-h, --help</td>
</tr> </tr>

33
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_apply.md
View File

@ -106,14 +106,18 @@ Perform the upgrade of etcd.
</tr> </tr>
<tr> <tr>
<td colspan="2">-k, --experimental-kustomize string</td> <td colspan="2">--experimental-patches string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- <!--
The path where kustomize patches for static pod manifests are stored. 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.
--> -->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。 包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
例如，"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</td> </td>
</tr> </tr>
@ -125,7 +129,9 @@ The path where kustomize patches for static pod manifests are stored.
<!-- <!--
A set of key=value pairs that describe feature gates for various features. Options are:<br/>IPv6DualStack=true|false (ALPHA - default=false) A set of key=value pairs that describe feature gates for various features. Options are:<br/>IPv6DualStack=true|false (ALPHA - default=false)
--> -->
一组键值对，用于描述各种功能。选项包括：<br/>IPv6DualStack=true|false (ALPHA - 默认值=false) 一组键值对，用于描述各种功能。选项包括：
<br/>IPv6DualStack=true|false (ALPHA - 默认=false)
<br/>PublicKeysECDSA=true|false (ALPHA - 默认=false)
</td> </td>
</tr> </tr>
@ -165,23 +171,6 @@ A list of checks whose errors will be shown as warnings. Example: 'IsPrivilegedU
</td> </td>
</tr> </tr>
<tr>
<td colspan="2">
<!--
--image-pull-timeout duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 15m0s
-->
--image-pull-timeout duration&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;默认值：15m0s
</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
The maximum amount of time to wait for the control plane pods to be downloaded.
-->
等待控制面板 pod 下载的最长时间。
</td>
</tr>
<tr> <tr>
<td colspan="2"> <td colspan="2">
<!-- <!--

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

@ -19,12 +19,14 @@ The "node" command executes the following phases:
<!-- <!--
``` ```
preflight Run upgrade node pre-flight checks
control-plane Upgrade the control plane instance deployed on this node, if any control-plane Upgrade the control plane instance deployed on this node, if any
kubelet-config Upgrade the kubelet configuration for this node kubelet-config Upgrade the kubelet configuration for this node
``` ```
--> -->
``` ```
preflight 执行节点升级前检查
control-plane 如果存在的话，升级部署在该节点上的管理面实例 control-plane 如果存在的话，升级部署在该节点上的管理面实例
kubelet-config 更新该节点上的 kubelet 配置 kubelet-config 更新该节点上的 kubelet 配置
``` ```
@ -87,14 +89,18 @@ Perform the upgrade of etcd.
</tr> </tr>
<tr> <tr>
<td colspan="2">-k, --experimental-kustomize string</td> <td colspan="2">--experimental-patches string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;"> <td></td><td style="line-height: 130%; word-wrap: break-word;">
<!-- <!--
The path where kustomize patches for static pod manifests are stored. 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.
--> -->
用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。 包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
例如，"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</td> </td>
</tr> </tr>

13
content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_node_phase_control-plane.md
View File

@ -62,10 +62,19 @@ kubeadm upgrade node phase control-plane [flags]
--> -->
<tr> <tr>
<td colspan="2">-k, --experimental-kustomize string</td> <td colspan="2">--experimental-patches string</td>
</tr> </tr>
<tr> <tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。</td> <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" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
</td>
</tr> </tr>
<!-- <!--