Skip to content

Commit 8ee8fe7

Browse files
authored
Merge pull request #40219 from asa3311/Reference-files-to-sync-task-13
[zh-cn]Reference files to sync task 13
2 parents 9864647 + ff33e1c commit 8ee8fe7

File tree

4 files changed

+45
-5
lines changed

4 files changed

+45
-5
lines changed

content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_kubelet-start.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,20 @@ you have more than one CRI installed or if you have non-standard CRI socket.
7676
</td>
7777
</tr>
7878

79+
<tr>
80+
<td colspan="2">--dry-run</td>
81+
</tr>
82+
<tr>
83+
<td></td><td style="line-height: 130%; word-wrap: break-word;">
84+
<!--
85+
Don't apply any changes; just output what would be done.
86+
-->
87+
<p>
88+
不做任何更改;只输出将要执行的操作。
89+
</p>
90+
</td>
91+
</tr>
92+
7993
<tr>
8094
<td colspan="2">-h, --help</td>
8195
</tr>

content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_join_phase_control-plane-prepare_all.md

Lines changed: 18 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ The file is auto-generated from the Go source code of the component using a gene
33
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
44
to generate the reference documentation, please read
55
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
6-
To update the reference conent, please follow the
6+
To update the reference content, please follow the
77
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
88
guide. You can file document formatting bugs against the
99
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
@@ -97,7 +97,7 @@ Use this key to decrypt the certificate secrets uploaded by init.
9797
<tr>
9898
<td></td><td style="line-height: 130%; word-wrap: break-word;">
9999
<!--
100-
Path to kubeadm config file.
100+
Path to a kubeadm configuration file.
101101
-->
102102
<p>
103103
kubeadm 配置文件的路径。
@@ -175,6 +175,20 @@ For token-based discovery, allow joining without --discovery-token-ca-cert-hash
175175
</td>
176176
</tr>
177177

178+
<tr>
179+
<td colspan="2">--dry-run</td>
180+
</tr>
181+
<tr>
182+
<td></td><td style="line-height: 130%; word-wrap: break-word;">
183+
<!--
184+
Don't apply any changes; just output what would be done.
185+
-->
186+
<p>
187+
不做任何更改;只输出将要执行的操作。
188+
</p>
189+
</td>
190+
</tr>
191+
178192
<tr>
179193
<td colspan="2">-h, --help</td>
180194
</tr>
@@ -207,12 +221,12 @@ Specify the node name.
207221
<tr>
208222
<td></td><td style="line-height: 130%; word-wrap: break-word;">
209223
<!--
210-
Path to a directory that contains files named &quot;target[suffix][+patchtype].extension&quot;. For example, &quot;kube-apiserver0+merge.yaml&quot; or just &quot;etcd.json&quot;. &quot;target&quot; can be one of &quot;kube-apiserver&quot;, &quot;kube-controller-manager&quot;, &quot;kube-scheduler&quot;, &quot;etcd&quot;. &quot;patchtype&quot; can be one of &quot;strategic&quot;, &quot;merge&quot; or &quot;json&quot; and they match the patch formats supported by kubectl. The default &quot;patchtype&quot; is &quot;strategic&quot;. &quot;extension&quot; must be either &quot;json&quot; or &quot;yaml&quot;. &quot;suffix&quot; is an optional string that can be used to determine which patches are applied first alpha-numerically.
224+
Path to a directory that contains files named &quot;target[suffix][+patchtype].extension&quot;. For example, &quot;kube-apiserver0+merge.yaml&quot; or just &quot;etcd.json&quot;. &quot;target&quot; can be one of &quot;kube-apiserver&quot;, &quot;kube-controller-manager&quot;, &quot;kube-scheduler&quot;, &quot;etcd&quot;, &quot;kubeletconfiguration&quot;. &quot;patchtype&quot; can be one of &quot;strategic&quot;, &quot;merge&quot; or &quot;json&quot; and they match the patch formats supported by kubectl. The default &quot;patchtype&quot; is &quot;strategic&quot;. &quot;extension&quot; must be either &quot;json&quot; or &quot;yaml&quot;. &quot;suffix&quot; is an optional string that can be used to determine which patches are applied first alpha-numerically.
211225
-->
212226
<p>
213227
包含名为 “target[suffix][+patchtype].extension” 的文件的目录的路径。
214228
例如,“kube-apiserver0+merge.yaml” 或只是 “etcd.json”。
215-
“target” 可以是 “kube-apiserver”、“kube-controller-manager”、“kube-scheduler”、“etcd” 之一。
229+
“target” 可以是 “kube-apiserver”、“kube-controller-manager”、“kube-scheduler”、“etcd”、“kubeletconfiguration” 之一。
216230
“patchtype” 可以是 “strategic”、“merge” 或 “json”,它们匹配 kubectl 支持的补丁格式。
217231
默认的 “patchtype” 是 “strategic”。“extension” 必须是 “json” 或 “yaml”。
218232
“suffix” 是一个可选字符串,可用于基于字母数字顺序确定首先应用哪些补丁。

content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,15 @@
1+
<!--
2+
The file is auto-generated from the Go source code of the component using a generic
3+
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
4+
to generate the reference documentation, please read
5+
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
6+
To update the reference content, please follow the
7+
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
8+
guide. You can file document formatting bugs against the
9+
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
10+
-->
11+
12+
113
<!--
214
Upgrade your cluster smoothly to a newer version with this command
315
-->

content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_upgrade_diff.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ The file is auto-generated from the Go source code of the component using a gene
33
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
44
to generate the reference documentation, please read
55
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
6-
To update the reference conent, please follow the
6+
To update the reference content, please follow the
77
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
88
guide. You can file document formatting bugs against the
99
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.

0 commit comments

Comments
 (0)