Reference files to sync task 23 (#40262)
xin gu
GitHub
parent
c94d325144
commit
2639ea6cc9
|
|
@ -46,19 +46,32 @@ kubeadm 配置文件的路径。
|
|||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--dry-run</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Don't apply any changes; just output what would be done.
|
||||
-->
|
||||
<p>
|
||||
不做任何更改；只输出将要执行的操作。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--feature-gates string</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<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/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)<br/>UnversionedKubeletConfigMap=true|false (default=true)
|
||||
A set of key=value pairs that describe feature gates for various features. Options are:<br/>PublicKeysECDSA=true|false (ALPHA - default=false)<br/>RootlessControlPlane=true|false (ALPHA - default=false)
|
||||
-->
|
||||
<p>
|
||||
一组用来描述各种特性门控的键值（key=value）对。选项是：
|
||||
<br/>PublicKeysECDSA=true|false (ALPHA - 默认值=false)
|
||||
<br/>RootlessControlPlane=true|false (ALPHA - 默认值=false)
|
||||
<br/>UnversionedKubeletConfigMap=true|false (默认值=true)
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ The file is auto-generated from the Go source code of the component using a gene
|
|||
[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
|
||||
To update the reference content, 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.
|
||||
|
|
@ -120,6 +120,20 @@ kubeadm init phase certs apiserver [flags]
|
|||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--dry-run</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Don't apply any changes; just output what would be done.
|
||||
-->
|
||||
<p>
|
||||
不做任何更改；只输出将要执行的操作。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">-h, --help</td>
|
||||
</tr>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ The file is auto-generated from the Go source code of the component using a gene
|
|||
[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
|
||||
To update the reference content, 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.
|
||||
|
|
@ -84,6 +84,20 @@ kubeadm init phase certs front-proxy-ca [flags]
|
|||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--dry-run</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Don't apply any changes; just output what would be done.
|
||||
-->
|
||||
<p>
|
||||
不做任何更改；只输出将要执行的操作。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">-h, --help</td>
|
||||
</tr>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ The file is auto-generated from the Go source code of the component using a gene
|
|||
[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
|
||||
To update the reference content, 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.
|
||||
|
|
@ -113,6 +113,20 @@ kubeadm init phase kubeconfig admin [flags]
|
|||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--dry-run</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Don't apply any changes; just output what would be done.
|
||||
-->
|
||||
<p>
|
||||
不做任何更改；只输出将要执行的操作。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">-h, --help</td>
|
||||
</tr>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ The file is auto-generated from the Go source code of the component using a gene
|
|||
[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
|
||||
To update the reference content, 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.
|
||||
|
|
@ -78,7 +78,7 @@ kubeadm join phase control-plane-prepare control-plane [flags]
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
<p>Path to kubeadm config file.</p>
|
||||
<p>Path to a kubeadm configuration file.</p>
|
||||
-->
|
||||
<p>kubeadm 配置文件的路径。</p>
|
||||
</td>
|
||||
|
|
@ -96,6 +96,20 @@ kubeadm join phase control-plane-prepare control-plane [flags]
|
|||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--dry-run</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Don't apply any changes; just output what would be done.
|
||||
-->
|
||||
<p>
|
||||
不做任何更改；只输出将要执行的操作。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">-h, --help</td>
|
||||
</tr>
|
||||
|
|
@ -113,14 +127,18 @@ kubeadm join phase control-plane-prepare control-plane [flags]
|
|||
</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". "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.</p>
|
||||
<!--
|
||||
<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", "kubeletconfiguration". "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. </p>
|
||||
-->
|
||||
<p>包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
|
||||
例如，"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
|
||||
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
|
||||
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
|
||||
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。</p>
|
||||
<p>包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
|
||||
例如 "kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
|
||||
"target" 可以是 "kube-apiserver"、"kube-controller-manager"、
|
||||
"kube-scheduler"、"etcd"、"kubeletconfiguration" 之一。
|
||||
"patchtype" 可以是 "strategic"、"merge" 或者 "json" 之一，
|
||||
并且它们与 kubectl 支持的补丁格式相同。
|
||||
默认的 "patchtype" 是 "strategic"。
|
||||
"extension" 必须是 "json" 或 "yaml"。
|
||||
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue