File tree Expand file tree Collapse file tree 1 file changed +7
-4
lines changed
content/zh/docs/tasks/access-application-cluster Expand file tree Collapse file tree 1 file changed +7
-4
lines changed Original file line number Diff line number Diff line change @@ -190,13 +190,16 @@ traffic spreading.
190
190
191
191
<!--
192
192
* `service.spec.healthCheckNodePort` - specifies the health check nodePort
193
- (numeric port number) for the service. If not specified, `healthCheckNodePort` is
194
- created by the service API backend with the allocated `nodePort`. It will use the
195
- user-specified `nodePort` value if specified by the client. It only has an
193
+ (numeric port number) for the service. If `healthCheckNodePort` isn't specified,
194
+ the service controller allocates a port from your cluster's NodePort range. You
195
+ can configure that range by setting an API server command line option,
196
+ ` --service-node-port-range` . It will use the
197
+ user-specified `healthCheckNodePort` value if specified by the client. It only has an
196
198
effect when `type` is set to LoadBalancer and `externalTrafficPolicy` is set
197
199
to Local.
198
200
-->
199
- * `service.spec.healthCheckNodePort` - 指定服务的 healthcheck nodePort(数字端口号)。如果未指定,则 serviceCheckNodePort 由服务 API 后端使用已分配的 nodePort 创建。如果客户端指定,它将使用客户端指定的 nodePort 值。仅当 type 设置为 LoadBalancer 并且 externalTrafficPolicy 设置为 Local 时才生效。
201
+
202
+ * `service.spec.healthCheckNodePort` - 指定服务的 healthcheck nodePort(数字端口号)。如果未指定 `healthCheckNodePort`,服务控制器从集群的 NodePort 范围内分配一个端口。您可以通过设置 API 服务器的命令行选项 `--service-node-port-range` 来配置上述范围。它将会使用用户指定的 `healthCheckNodePort` 值(如果被客户端指定)。仅当 `type` 设置为 LoadBalancer 并且 `externalTrafficPolicy` 设置为 Local 时才生效。
200
203
201
204
<!--
202
205
Setting `externalTrafficPolicy` to Local in the Service configuration file
You can’t perform that action at this time.
0 commit comments