You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optional extra Subject Alternative Names (SANs) to use for the API Server serving certificate. Can be both IP addresses and DNS names.
112
131
-->
132
+
<p>
113
133
用于 API Server 服务证书的可选附加主题备用名称(SAN)。可以是 IP 地址和 DNS 名称。
134
+
</p>
114
135
</td>
115
136
</tr>
116
137
@@ -127,7 +148,9 @@ Optional extra Subject Alternative Names (SANs) to use for the API Server servin
127
148
<!--
128
149
The path where to save and store the certificates.
129
150
-->
151
+
<p>
130
152
保存和存储证书的路径。
153
+
</p>
131
154
</td>
132
155
</tr>
133
156
@@ -139,7 +162,9 @@ The path where to save and store the certificates.
139
162
<!--
140
163
Key used to encrypt the control-plane certificates in the kubeadm-certs Secret.
141
164
-->
165
+
<p>
142
166
用于加密 kubeadm-certs Secret 中的控制平面证书的密钥。
167
+
</p>
143
168
</td>
144
169
</tr>
145
170
@@ -151,7 +176,9 @@ Key used to encrypt the control-plane certificates in the kubeadm-certs Secret.
151
176
<!--
152
177
Path to a kubeadm configuration file.
153
178
-->
179
+
<p>
154
180
kubeadm 配置文件的路径。
181
+
</p>
155
182
</td>
156
183
</tr>
157
184
@@ -163,7 +190,9 @@ kubeadm 配置文件的路径。
163
190
<!--
164
191
Specify a stable IP address or DNS name for the control plane.
165
192
-->
193
+
<p>
166
194
为控制平面指定一个稳定的 IP 地址或 DNS 名称。
195
+
</p>
167
196
</td>
168
197
</tr>
169
198
@@ -175,7 +204,9 @@ Specify a stable IP address or DNS name for the control plane.
175
204
<!--
176
205
Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.
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.
A set of key=value pairs that describe feature gates for various features. Options are:<br/>IPv6DualStack=true|false (ALPHA - default=false)
233
+
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 (BETA - default=true)
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.
The token to use for establishing bidirectional trust between nodes and control-plane nodes. The format is [a-z0-9]{6}\.[a-z0-9]{16} - e.g. abcdef.0123456789abcdef
441
+
The token to use for establishing bidirectional trust between nodes and control-plane nodes. The format is [a-z0-9]{6}.[a-z0-9]{16} - e.g. abcdef.0123456789abcdef
0 commit comments