Skip to content

Commit 2639ea6

Browse files
authored
Reference files to sync task 23 (#40262)
1 parent c94d325 commit 2639ea6

File tree

5 files changed

+87
-14
lines changed

5 files changed

+87
-14
lines changed

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

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,19 +46,32 @@ kubeadm 配置文件的路径。
4646
</td>
4747
</tr>
4848

49+
<tr>
50+
<td colspan="2">--dry-run</td>
51+
</tr>
52+
<tr>
53+
<td></td><td style="line-height: 130%; word-wrap: break-word;">
54+
<!--
55+
Don't apply any changes; just output what would be done.
56+
-->
57+
<p>
58+
不做任何更改;只输出将要执行的操作。
59+
</p>
60+
</td>
61+
</tr>
62+
4963
<tr>
5064
<td colspan="2">--feature-gates string</td>
5165
</tr>
5266
<tr>
5367
<td></td><td style="line-height: 130%; word-wrap: break-word;">
5468
<!--
55-
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)
69+
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)
5670
-->
5771
<p>
5872
一组用来描述各种特性门控的键值(key=value)对。选项是:
5973
<br/>PublicKeysECDSA=true|false (ALPHA - 默认值=false)
6074
<br/>RootlessControlPlane=true|false (ALPHA - 默认值=false)
61-
<br/>UnversionedKubeletConfigMap=true|false (默认值=true)
6275
</p>
6376
</td>
6477
</tr>

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

Lines changed: 15 additions & 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.
@@ -120,6 +120,20 @@ kubeadm init phase certs apiserver [flags]
120120
</td>
121121
</tr>
122122

123+
<tr>
124+
<td colspan="2">--dry-run</td>
125+
</tr>
126+
<tr>
127+
<td></td><td style="line-height: 130%; word-wrap: break-word;">
128+
<!--
129+
Don't apply any changes; just output what would be done.
130+
-->
131+
<p>
132+
不做任何更改;只输出将要执行的操作。
133+
</p>
134+
</td>
135+
</tr>
136+
123137
<tr>
124138
<td colspan="2">-h, --help</td>
125139
</tr>

content/zh-cn/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_certs_front-proxy-ca.md

Lines changed: 15 additions & 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.
@@ -84,6 +84,20 @@ kubeadm init phase certs front-proxy-ca [flags]
8484
</td>
8585
</tr>
8686

87+
<tr>
88+
<td colspan="2">--dry-run</td>
89+
</tr>
90+
<tr>
91+
<td></td><td style="line-height: 130%; word-wrap: break-word;">
92+
<!--
93+
Don't apply any changes; just output what would be done.
94+
-->
95+
<p>
96+
不做任何更改;只输出将要执行的操作。
97+
</p>
98+
</td>
99+
</tr>
100+
87101
<tr>
88102
<td colspan="2">-h, --help</td>
89103
</tr>

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

Lines changed: 15 additions & 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.
@@ -113,6 +113,20 @@ kubeadm init phase kubeconfig admin [flags]
113113
</td>
114114
</tr>
115115

116+
<tr>
117+
<td colspan="2">--dry-run</td>
118+
</tr>
119+
<tr>
120+
<td></td><td style="line-height: 130%; word-wrap: break-word;">
121+
<!--
122+
Don't apply any changes; just output what would be done.
123+
-->
124+
<p>
125+
不做任何更改;只输出将要执行的操作。
126+
</p>
127+
</td>
128+
</tr>
129+
116130
<tr>
117131
<td colspan="2">-h, --help</td>
118132
</tr>

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

Lines changed: 27 additions & 9 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.
@@ -78,7 +78,7 @@ kubeadm join phase control-plane-prepare control-plane [flags]
7878
<tr>
7979
<td></td><td style="line-height: 130%; word-wrap: break-word;">
8080
<!--
81-
<p>Path to kubeadm config file.</p>
81+
<p>Path to a kubeadm configuration file.</p>
8282
-->
8383
<p>kubeadm 配置文件的路径。</p>
8484
</td>
@@ -96,6 +96,20 @@ kubeadm join phase control-plane-prepare control-plane [flags]
9696
</td>
9797
</tr>
9898

99+
<tr>
100+
<td colspan="2">--dry-run</td>
101+
</tr>
102+
<tr>
103+
<td></td><td style="line-height: 130%; word-wrap: break-word;">
104+
<!--
105+
Don't apply any changes; just output what would be done.
106+
-->
107+
<p>
108+
不做任何更改;只输出将要执行的操作。
109+
</p>
110+
</td>
111+
</tr>
112+
99113
<tr>
100114
<td colspan="2">-h, --help</td>
101115
</tr>
@@ -113,14 +127,18 @@ kubeadm join phase control-plane-prepare control-plane [flags]
113127
</tr>
114128
<tr>
115129
<td></td><td style="line-height: 130%; word-wrap: break-word;">
116-
<!--
117-
<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>
130+
<!--
131+
<p>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. </p>
118132
-->
119-
<p>包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
120-
例如,"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
121-
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一,并且它们与 kubectl 支持的补丁格式匹配。
122-
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
123-
"suffix" 是一个可选字符串,可用于确定首先按字母顺序应用哪些补丁。</p>
133+
<p>包含名为 &quot;target[suffix][+patchtype].extension&quot; 的文件的目录的路径。
134+
例如 &quot;kube-apiserver0+merge.yaml&quot; 或仅仅是 &quot;etcd.json&quot;
135+
&quot;target&quot; 可以是 &quot;kube-apiserver&quot;&quot;kube-controller-manager&quot;
136+
&quot;kube-scheduler&quot;&quot;etcd&quot;&quot;kubeletconfiguration&quot; 之一。
137+
&quot;patchtype&quot; 可以是 &quot;strategic&quot;&quot;merge&quot; 或者 &quot;json&quot; 之一,
138+
并且它们与 kubectl 支持的补丁格式相同。
139+
默认的 &quot;patchtype&quot;&quot;strategic&quot;
140+
&quot;extension&quot; 必须是 &quot;json&quot;&quot;yaml&quot;
141+
&quot;suffix&quot; 是一个可选字符串,可用于确定首先按字母顺序应用哪些补丁。</p>
124142
</td>
125143
</tr>
126144

0 commit comments

Comments
 (0)