Reference files to sync task 8
xin gu
parent
fbeadc1f07
commit
138fc4fba1
|
|
@ -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.
|
||||
|
|
|
|||
|
|
@ -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.
|
||||
|
|
@ -63,7 +63,7 @@ If the node should host a new control plane instance, the IP address the API Ser
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Path to kubeadm configuration file.
|
||||
Path to a kubeadm configuration file.
|
||||
-->
|
||||
<p>
|
||||
kubeadm 配置文件的路径。
|
||||
|
|
@ -85,6 +85,20 @@ Create a new control plane instance on this node
|
|||
</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>
|
||||
|
|
@ -117,10 +131,10 @@ Specify the node name.
|
|||
</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. -->
|
||||
<!-- 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. -->
|
||||
包含名为 “target[suffix][+patchtype].extension” 的文件的目录的路径。
|
||||
例如，“kube-apiserver0+merge.yaml” 或只是 “etcd.json”。
|
||||
“target” 可以是 “kube-apiserver”、“kube-controller-manager”、“kube-scheduler”、“etcd” 之一。
|
||||
“target” 可以是 “kube-apiserver”、“kube-controller-manager”、“kube-scheduler”、“etcd” 、”kubeletconfiguration”之一。
|
||||
“patchtype” 可以是 “strategic”、“merge” 或 “json”，它们匹配 kubectl 支持的补丁格式。
|
||||
默认的 “patchtype” 是 “strategic”。“extension” 必须是 “json” 或 “yaml”。
|
||||
“suffix” 是一个可选字符串，可用于基于字母数字顺序确定首先应用哪些补丁。
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ kubeadm join phase kubelet-start [api-server-endpoint] [flags]
|
|||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
Path to kubeadm config file.
|
||||
Path to a kubeadm configuration file.
|
||||
-->
|
||||
kubeadm 配置文件的路径。
|
||||
</td>
|
||||
|
|
@ -126,6 +126,20 @@ For token-based discovery, allow joining without --discovery-token-ca-cert-hash
|
|||
</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.
|
||||
|
|
|
|||
Loading…
Reference in New Issue