Merge pull request #33813 from JarHMJ/kubeadm-20
[zh] sync v1.24 kubeadm-20
This commit is contained in:
@@ -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.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Manage configuration for a kubeadm cluster persisted in a ConfigMap in the cluster
|
||||
-->
|
||||
管理持久化在 ConfigMap 中的 kubeadm 集群的配置
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
@@ -41,8 +56,10 @@ kubeadm config [flags]
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- help for config -->
|
||||
config 操作的帮助命令
|
||||
<!--
|
||||
<p>help for config</p>
|
||||
-->
|
||||
<p>config 操作的帮助命令</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -56,10 +73,11 @@ config 操作的帮助命令
|
||||
</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.
|
||||
<!--
|
||||
<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 文件。如果它没有被设置,那么 kubeadm 将会搜索一个已经存在于标准路径的 kubeconfig 文件
|
||||
<p>用于和集群通信的 kubeconfig 文件。如果它没有被设置,那么 kubeadm 将会搜索一个已经存在于标准路径的 kubeconfig 文件
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -84,8 +102,10 @@ If the flag is not set, a set of standard locations can be searched for an exist
|
||||
</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>[实验] 到 '真实' 主机根文件系统的路径。
|
||||
</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.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Read an older version of the kubeadm configuration API types from a file, and output the similar config object for the newer version
|
||||
-->
|
||||
从文件中读取旧版本的 kubeadm 配置的 API 类型,并为新版本输出类似的配置对象
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
@@ -9,12 +24,11 @@
|
||||
This command lets you convert configuration objects of older versions to the latest supported version,
|
||||
locally in the CLI tool without ever touching anything in the cluster.
|
||||
In this version of kubeadm, the following API versions are supported:
|
||||
- kubeadm.k8s.io/v1beta2
|
||||
- kubeadm.k8s.io/v1beta3
|
||||
-->
|
||||
|
||||
此命令允许您在 CLI 工具中将本地旧版本的配置对象转换为最新支持的版本,而无需变更集群中的任何内容。在此版本的 kubeadm 中,支持以下 API 版本:
|
||||
|
||||
- kubeadm.k8s.io/v1beta2
|
||||
- kubeadm.k8s.io/v1beta3
|
||||
|
||||
<!--
|
||||
Further, kubeadm can only write out config of version "kubeadm.k8s.io/v1beta2", but read both types.
|
||||
@@ -55,8 +69,10 @@ kubeadm config migrate [flags]
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- help for migrate -->
|
||||
migrate 操作的帮助信息
|
||||
<!--
|
||||
<p>help for migrate</p>
|
||||
-->
|
||||
<p>migrate 操作的帮助信息</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -66,9 +82,9 @@ migrate 操作的帮助信息
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Path to the resulting equivalent kubeadm config file using the new API version. Optional, if not specified output will be sent to STDOUT.
|
||||
<p>Path to the resulting equivalent kubeadm config file using the new API version. Optional, if not specified output will be sent to STDOUT.</p>
|
||||
-->
|
||||
使用新的 API 版本生成的 kubeadm 配置文件的路径。这个路径是可选的。如果没有指定,输出将被写到 stdout。
|
||||
<p>使用新的 API 版本生成的 kubeadm 配置文件的路径。这个路径是可选的。如果没有指定,输出将被写到 stdout。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -78,9 +94,9 @@ Path to the resulting equivalent kubeadm config file using the new API version.
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Path to the kubeadm config file that is using an old API version and should be converted. This flag is mandatory.
|
||||
<p>Path to the kubeadm config file that is using an old API version and should be converted. This flag is mandatory.</p>
|
||||
-->
|
||||
使用旧 API 版本且应转换的 kubeadm 配置文件的路径。此参数是必需的。
|
||||
<p>使用旧 API 版本且应转换的 kubeadm 配置文件的路径。此参数是必需的。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -109,9 +125,9 @@ Path to the kubeadm config file that is using an old API version and should be c
|
||||
<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 文件。如果未设置,那么 kubeadm 将会搜索一个已经存在于标准路径的 kubeconfig 文件。
|
||||
<p>用于和集群通信的 kubeconfig 文件。如果未设置,那么 kubeadm 将会搜索一个已经存在于标准路径的 kubeconfig 文件。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -120,8 +136,10 @@ The kubeconfig file to use when talking to the cluster. If the flag is not set,
|
||||
</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.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Use this command to invoke single phase of the join workflow
|
||||
-->
|
||||
使用此命令来调用 `join` 工作流程的某个阶段
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
@@ -29,8 +44,10 @@ Use this command to invoke single phase of the join 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>
|
||||
|
||||
@@ -55,8 +72,10 @@ phase 操作的帮助命令
|
||||
</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>
|
||||
|
||||
|
||||
+39
-14
@@ -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.
|
||||
-->
|
||||
|
||||
<!--
|
||||
Register the new control-plane node into the ClusterStatus maintained in the kubeadm-config ConfigMap (DEPRECATED)
|
||||
-->
|
||||
将新的控制平面节点注册到 kubeadm-config ConfigMap 维护的 ClusterStatus 中(已弃用)
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
@@ -6,10 +21,10 @@
|
||||
## 概要
|
||||
|
||||
<!--
|
||||
Register the new control-plane node into the ClusterStatus maintained in the kubeadm-config ConfigMap
|
||||
Register the new control-plane node into the ClusterStatus maintained in the kubeadm-config ConfigMap (DEPRECATED)
|
||||
-->
|
||||
|
||||
将新的控制平面节点注册到 kubeadm-config ConfigMap 维护的 ClusterStatus 中
|
||||
将新的控制平面节点注册到 kubeadm-config ConfigMap 维护的 ClusterStatus 中(已弃用)
|
||||
|
||||
```
|
||||
kubeadm join phase control-plane-join update-status [flags]
|
||||
@@ -34,9 +49,9 @@ kubeadm join phase control-plane-join update-status [flags]
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
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>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>如果该节点托管一个新的控制平面实例,则 API 服务器将公布其正在侦听的 IP 地址。如果未设置,则使用默认网络接口。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -45,8 +60,10 @@ If the node should host a new control plane instance, the IP address the API Ser
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- Path to kubeadm config file. -->
|
||||
kubeadm 配置文件的路径。
|
||||
<!--
|
||||
<p>Path to kubeadm config file.</p>
|
||||
-->
|
||||
<p>kubeadm 配置文件的路径。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -55,8 +72,10 @@ kubeadm 配置文件的路径。
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- Create a new control plane instance on this node -->
|
||||
在此节点上创建一个新的控制平面实例
|
||||
<!--
|
||||
<p>Create a new control plane instance on this node</p>
|
||||
-->
|
||||
<p>在此节点上创建一个新的控制平面实例</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -65,8 +84,10 @@ kubeadm 配置文件的路径。
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- help for update-status -->
|
||||
update-status 操作的帮助命令
|
||||
<!--
|
||||
<p>help for update-status</p>
|
||||
-->
|
||||
<p>update-status 操作的帮助命令</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -75,8 +96,10 @@ update-status 操作的帮助命令
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!-- Specify the node name. -->
|
||||
指定节点名称。
|
||||
<!--
|
||||
<p>Specify the node name.</p>
|
||||
-->
|
||||
<p>指定节点名称。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -103,8 +126,10 @@ update-status 操作的帮助命令
|
||||
</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>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user