Merge pull request #33489 from nameYULI/yl10
[zh]Update content/zh/docs/reference/setup-tools/kubeadm/generated/kubeadm_init_phase_control-plane_apiserver.mdpull/33525/head
Kubernetes Prow Robot
GitHub
commit
0bf578ea05
|
|
@ -1,3 +1,8 @@
|
|||
<!--
|
||||
Generates the kube-apiserver static Pod manifest
|
||||
-->
|
||||
生成 kube-apiserver 静态 Pod 清单
|
||||
|
||||
<!--
|
||||
### Synopsis
|
||||
-->
|
||||
|
|
@ -32,7 +37,9 @@ kubeadm init phase control-plane apiserver [flags]
|
|||
<!--
|
||||
The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
|
||||
-->
|
||||
<p>
|
||||
API 服务器所公布的其正在监听的 IP 地址。如果未设置，将使用默认网络接口。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -49,20 +56,24 @@ API 服务器所公布的其正在监听的 IP 地址。如果未设置，将使
|
|||
<!--
|
||||
Port for the API Server to bind to.
|
||||
-->
|
||||
<p>
|
||||
要绑定到 API 服务器的端口。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--apiserver-extra-args mapStringString</td>
|
||||
<td colspan="2">--apiserver-extra-args <!--<comma-separated 'key=value' pairs>--><逗号分隔的 'key=value' 对></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
A set of extra flags to pass to the API Server or override default ones in form of <flagname>=<value>
|
||||
-->
|
||||
<p>
|
||||
一组 <flagname>=<value> 形式的额外参数，用来传递给 API 服务器
|
||||
或者覆盖其默认参数配置
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -79,7 +90,9 @@ A set of extra flags to pass to the API Server or override default ones in form
|
|||
<!--
|
||||
The path where to save and store the certificates.
|
||||
-->
|
||||
<p>
|
||||
保存和存储证书的路径。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -91,7 +104,9 @@ The path where to save and store the certificates.
|
|||
<!--
|
||||
Path to a kubeadm configuration file.
|
||||
-->
|
||||
<p>
|
||||
kubeadm 配置文件的路径。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -103,21 +118,24 @@ kubeadm 配置文件的路径。
|
|||
<!--
|
||||
Specify a stable IP address or DNS name for the control plane.
|
||||
-->
|
||||
<p>
|
||||
为控制平面指定一个稳定的 IP 地址或 DNS 名称。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--dry-run</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--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.-->
|
||||
包含名为 "target[suffix][+patchtype].extension" 的文件的目录。
|
||||
例如，"kube-apiserver0+merge.yaml" 或者 "etcd.json"。
|
||||
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，分别与 kubectl
|
||||
所支持的 patch 格式相匹配。默认的 "patchtype" 是 "strategic"。
|
||||
"extension" 必须是 "json" 或 "yaml"。
|
||||
"suffix" 是一个可选的字符串，用来确定按字母顺序排序时首先应用哪些 patch。
|
||||
<!--
|
||||
Don't apply any changes; just output what would be done.
|
||||
-->
|
||||
<p>
|
||||
不要应用任何更改；只是输出将要执行的操作。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--feature-gates string</td>
|
||||
|
|
@ -125,11 +143,14 @@ Specify a stable IP address or DNS name for the control plane.
|
|||
<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/>IPv6DualStack=true|false (ALPHA - default=false)<br/>PublicKeysECDSA=true|false (ALPHA - default=false)
|
||||
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)
|
||||
-->
|
||||
<p>
|
||||
一组键值对，用于描述各种功能特性的特性门控。选项是：
|
||||
<br/>IPv6DualStack=true|false (ALPHA - 默认=false)
|
||||
<br/>PublicKeysECDSA=true|false (ALPHA - 默认=false)
|
||||
<br/>PublicKeysECDSA=true|false (ALPHA - 默认值=false)
|
||||
<br/>RootlessControlPlane=true|false (ALPHA - 默认值=false)
|
||||
<br/>UnversionedKubeletConfigMap=true|false (BETA - 默认值=true)
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -141,7 +162,9 @@ A set of key=value pairs that describe feature gates for various features. Optio
|
|||
<!--
|
||||
help for apiserver
|
||||
-->
|
||||
<p>
|
||||
apiserver 操作的帮助命令
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -158,7 +181,9 @@ apiserver 操作的帮助命令
|
|||
<!--
|
||||
Choose a container registry to pull control plane images from
|
||||
-->
|
||||
<p>
|
||||
选择要从中拉取控制平面镜像的容器仓库
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -175,7 +200,30 @@ Choose a container registry to pull control plane images from
|
|||
<!--
|
||||
Choose a specific Kubernetes version for the control plane.
|
||||
-->
|
||||
<p>
|
||||
为控制平面选择特定的 Kubernetes 版本
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--patches string</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;">
|
||||
<!--
|
||||
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.
|
||||
-->
|
||||
<p>
|
||||
包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
|
||||
例如，"kube-apiserver0+merge.yaml"或仅仅是 "etcd.json"。
|
||||
"target" 可以是 "kube-apiserver"、"kube-controller-manager"、"kube-scheduler"、"etcd" 之一。
|
||||
"patchtype" 可以是 "strategic"、"merge" 或者 "json" 之一，
|
||||
并且它们与 kubectl 支持的补丁格式相同。
|
||||
默认的 "patchtype" 是 "strategic"。
|
||||
"extension" 必须是"json" 或"yaml"。
|
||||
"suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -192,7 +240,9 @@ Choose a specific Kubernetes version for the control plane.
|
|||
<!--
|
||||
Use alternative range of IP address for service VIPs.
|
||||
-->
|
||||
<p>
|
||||
指定服务 VIP 使用 IP 地址的其他范围。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
@ -221,7 +271,9 @@ Use alternative range of IP address for service VIPs.
|
|||
<!--
|
||||
[EXPERIMENTAL] The path to the 'real' host root filesystem.
|
||||
-->
|
||||
<p>
|
||||
[实验] 到 '真实' 主机根文件系统路径。
|
||||
</p>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue