Kubernetes Prow Robot
GitHub
commit
aa12eb656b
|
|
@ -9,7 +9,6 @@ guide. You can file document formatting bugs against the
|
|||
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
|
||||
-->
|
||||
|
||||
|
||||
Add a new local etcd member
|
||||
|
||||
### Synopsis
|
||||
|
|
|
|||
|
|
@ -123,6 +123,3 @@ kubeadm join phase kubelet-start [api-server-endpoint] [flags]
|
|||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -67,6 +67,3 @@ kubeadm reset phase remove-etcd-member [flags]
|
|||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Add a new local etcd member
|
||||
-->
|
||||
添加一个新的本地 etcd 成员
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
|
|
@ -36,7 +51,9 @@ kubeadm join phase control-plane-join etcd [flags]
|
|||
<!--
|
||||
If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
|
||||
-->
|
||||
<p>
|
||||
如果该节点托管一个新的控制平面实例，则 API 服务器将公布其正在侦听的 IP 地址。如果未设置，则使用默认网络接口。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -48,7 +65,9 @@ If the node should host a new control plane instance, the IP address the API Ser
|
|||
<!--
|
||||
Path to kubeadm configuration file.
|
||||
-->
|
||||
<p>
|
||||
kubeadm 配置文件的路径。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -60,23 +79,9 @@ kubeadm 配置文件的路径。
|
|||
<!--
|
||||
Create a new control plane instance on this node
|
||||
-->
|
||||
<p>
|
||||
在此节点上创建一个新的控制平面实例
|
||||
</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>
|
||||
|
||||
|
|
@ -88,7 +93,9 @@ Path to a directory that contains files named "target[suffix][+patchtype].extens
|
|||
<!--
|
||||
help for etcd
|
||||
-->
|
||||
<p>
|
||||
etcd 操作的帮助命令
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -100,9 +107,25 @@ etcd 操作的帮助命令
|
|||
<!--
|
||||
Specify the node name.
|
||||
-->
|
||||
<p>
|
||||
指定节点的名称
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td colspan="2">--patches string</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>
|
||||
<!-- Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd". "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”。
|
||||
“target” 可以是 “kube-apiserver”、“kube-controller-manager”、“kube-scheduler”、“etcd” 之一。
|
||||
“patchtype” 可以是 “strategic”、“merge” 或 “json”，它们匹配 kubectl 支持的补丁格式。
|
||||
默认的 “patchtype” 是 “strategic”。“extension” 必须是 “json” 或 “yaml”。
|
||||
“suffix” 是一个可选字符串，可用于基于字母数字顺序确定首先应用哪些补丁。
|
||||
</p></td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
|
@ -128,7 +151,9 @@ Specify the node name.
|
|||
<!--
|
||||
[EXPERIMENTAL] The path to the 'real' host root filesystem.
|
||||
-->
|
||||
<p>
|
||||
[实验] 到 '真实' 主机根文件系统的路径。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
-->
|
||||
|
||||
|
||||
<!--
|
||||
Write kubelet settings, certificates and (re)start the kubelet
|
||||
-->
|
||||
配置 Kubelet、证书并（重新）启动 Kubelet
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
|
|
@ -48,7 +64,9 @@ kubeadm 配置文件的路径。
|
|||
<!--
|
||||
Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
|
||||
-->
|
||||
<p>
|
||||
提供给 CRI 套接字建立连接的路径。如果为空，则 kubeadm 将尝试自动检测该值；仅当安装了多个 CRI 或具有非标准 CRI 套接字时，才使用此选项。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -57,11 +75,12 @@ Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this
|
|||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
For file-based discovery, a file or URL from which to load cluster information.
|
||||
<!--
|
||||
For file-based discovery, a file or URL from which to load cluster information.
|
||||
-->
|
||||
<p>
|
||||
对于基于文件的发现，给出用于加载集群信息的文件或者 URL。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -73,7 +92,9 @@ For file-based discovery, a file or URL from which to load cluster information.
|
|||
<!--
|
||||
For token-based discovery, the token used to validate cluster information fetched from the API server.
|
||||
-->
|
||||
<p>
|
||||
对于基于令牌的发现，该令牌用于验证从 API 服务器获取的集群信息。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -85,7 +106,9 @@ For token-based discovery, the token used to validate cluster information fetche
|
|||
<!--
|
||||
For token-based discovery, validate that the root CA public key matches this hash (format: "<type>:<value>").
|
||||
-->
|
||||
<p>
|
||||
对于基于令牌的发现，验证根 CA 公钥是否匹配此哈希值（格式："<type>:<value>"）。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -97,7 +120,9 @@ For token-based discovery, validate that the root CA public key matches this has
|
|||
<!--
|
||||
For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.
|
||||
-->
|
||||
<p>
|
||||
对于基于令牌的发现，允许在未关联 --discovery-token-ca-cert-hash 参数的情况下添加节点。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -109,7 +134,9 @@ For token-based discovery, allow joining without --discovery-token-ca-cert-hash
|
|||
<!--
|
||||
help for kubelet-start
|
||||
-->
|
||||
<p>
|
||||
kubelet-start 操作的帮助命令
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -121,7 +148,9 @@ kubelet-start 操作的帮助命令
|
|||
<!--
|
||||
Specify the node name.
|
||||
-->
|
||||
<p>
|
||||
指定节点名称。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -133,7 +162,9 @@ Specify the node name.
|
|||
<!--
|
||||
Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
|
||||
-->
|
||||
<p>
|
||||
指定在加入节点时用于临时通过 Kubernetes 控制平面进行身份验证的令牌。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -145,7 +176,9 @@ Specify the token used to temporarily authenticate with the Kubernetes Control P
|
|||
<!--
|
||||
Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.
|
||||
-->
|
||||
<p>
|
||||
如果未提供这些值，则将它们用于 discovery-token 令牌和 tls-bootstrap 令牌。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -173,10 +206,11 @@ Use this token for both discovery-token and tls-bootstrap-token when those value
|
|||
<!--
|
||||
[EXPERIMENTAL] The path to the 'real' host root filesystem.
|
||||
-->
|
||||
<p>
|
||||
[实验] 指向 '真实' 宿主机根文件系统的路径。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Remove a local etcd member.
|
||||
-->
|
||||
删除本地 etcd 成员
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
-->
|
||||
|
|
@ -5,13 +21,12 @@
|
|||
### 概要
|
||||
|
||||
<!--
|
||||
Upload configuration about the current state, so that 'kubeadm upgrade' can later know how to configure the upgraded cluster.
|
||||
Remove a local etcd member for a control plane node.
|
||||
-->
|
||||
|
||||
上传关于当前状态的配置，以便 'kubeadm upgrade' 以后可以知道如何配置升级后的集群。
|
||||
删除控制平面节点的本地 etcd 成员
|
||||
|
||||
```
|
||||
kubeadm config upload [flags]
|
||||
kubeadm reset phase remove-etcd-member [flags]
|
||||
```
|
||||
|
||||
<!--
|
||||
|
|
@ -31,7 +46,23 @@ kubeadm config upload [flags]
|
|||
<td colspan="2">-h, --help</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">upload 操作的帮助信息</td>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<p>
|
||||
<!-- help for remove-etcd-member -->
|
||||
remove-etcd-member 的帮助信息
|
||||
</p></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--kubeconfig string <!--Default:-->默认值："/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. -->
|
||||
与集群通信时使用的 Kubeconfig 文件。如果未设置该标志，则可以在默认位置中查找现有的 Kubeconfig 文件。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
|
|
@ -51,23 +82,17 @@ kubeadm config upload [flags]
|
|||
</colgroup>
|
||||
<tbody>
|
||||
|
||||
<tr>
|
||||
<!-- td colspan="2">kubeconfig string Default: "/etc/kubernetes/admin.conf"</td -->
|
||||
<td colspan="2">--kubeconfig string 默认值： "/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>
|
||||
|
||||
<tr>
|
||||
<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>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,69 +0,0 @@
|
|||
|
||||
<!--
|
||||
### Synopsis
|
||||
-->
|
||||
|
||||
### 概要
|
||||
|
||||
<!--
|
||||
Remove this node from the ClusterStatus object if the node is a control plane node.
|
||||
-->
|
||||
|
||||
如果该节点是控制平面节点，从 ClusterStatus 对象中删除该节点。
|
||||
|
||||
```
|
||||
kubeadm reset phase update-cluster-status [flags]
|
||||
```
|
||||
|
||||
<!--
|
||||
### Options
|
||||
-->
|
||||
|
||||
### 选项
|
||||
|
||||
<table style="width: 100%; table-layout: fixed;">
|
||||
<colgroup>
|
||||
<col span="1" style="width: 10px;" />
|
||||
<col span="1" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">-h, --help</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- help for update-cluster-status -->
|
||||
update-cluster-status 操作的帮助命令
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
<!--
|
||||
### Options inherited from parent commands
|
||||
-->
|
||||
|
||||
### 从父命令继承的选项
|
||||
|
||||
<table style="width: 100%; table-layout: fixed;">
|
||||
<colgroup>
|
||||
<col span="1" style="width: 10px;" />
|
||||
<col span="1" />
|
||||
</colgroup>
|
||||
<tbody>
|
||||
|
||||
<tr>
|
||||
<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>
|
||||
</tr>
|
||||
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
|
@ -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.
|
||||
-->
|
||||
|
||||
<!--
|
||||
List bootstrap tokens on the server
|
||||
-->
|
||||
列出服务器上的引导令牌
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
-->
|
||||
|
|
@ -8,7 +24,7 @@
|
|||
This command will list all bootstrap tokens for you.
|
||||
-->
|
||||
|
||||
此命令将为您列出所有的引导令牌。
|
||||
此命令将为你列出所有的引导令牌。
|
||||
|
||||
```
|
||||
kubeadm token list [flags]
|
||||
|
|
@ -38,8 +54,10 @@ kubeadm token list [flags]
|
|||
<!--
|
||||
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.
|
||||
-->
|
||||
<p>
|
||||
如果设置为 true，则在模板中缺少字段或哈希表的键时忽略模板中的任何错误。
|
||||
仅适用于 golang 和 jsonpath 输出格式。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -54,7 +72,9 @@ If true, ignore any errors in templates when a field or map key is missing in th
|
|||
<!--
|
||||
Output format. One of: text|json|yaml|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.
|
||||
-->
|
||||
<p>
|
||||
输出格式：text|json|yaml|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file 其中之一
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -64,7 +84,21 @@ Output format. One of: text|json|yaml|go-template|go-template-file|template|temp
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- help for list -->
|
||||
<p>
|
||||
list 操作的帮助命令
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--show-managed-fields</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<p>
|
||||
<!-- If true, keep the managedFields when printing objects in JSON or YAML format. -->
|
||||
如果为 true，则在以 JSON 或 YAML 格式打印对象时保留 managedFields。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -90,8 +124,10 @@ list 操作的帮助命令
|
|||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<p>
|
||||
<!-- Whether to enable dry-run mode or not -->
|
||||
是否启用 `dry-run` 模式
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -108,7 +144,9 @@ list 操作的帮助命令
|
|||
<!--
|
||||
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>
|
||||
|
||||
|
|
@ -118,7 +156,9 @@ The kubeconfig file to use when talking to the cluster. If the flag is not set,
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- [EXPERIMENTAL] The path to the 'real' host root filesystem. -->
|
||||
<p>
|
||||
[实验] 指向 '真实' 宿主机根文件系统的路径。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue