From c196466517f33d7c5e8c136446ada862200a5231 Mon Sep 17 00:00:00 2001 From: Fangyuan Li Date: Fri, 31 Jan 2020 09:24:08 -0800 Subject: [PATCH 1/2] Reduce ambiguity on nodePort At first sight, nodePort looks a lot like service.Spec.NodePort, though it just means a port allocated from "--service-node-port-range". Replacing "nodePort" with "node port" to add some clarity. --- .../create-external-load-balancer.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md b/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md index 3cf8c0a40be04..94cafb16d8022 100644 --- a/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md +++ b/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md @@ -127,10 +127,10 @@ IP and may cause a second hop to another node, but should have good overall load-spreading. Local preserves the client source IP and avoids a second hop for LoadBalancer and NodePort type services, but risks potentially imbalanced traffic spreading. -* `service.spec.healthCheckNodePort` - specifies the health check nodePort +* `service.spec.healthCheckNodePort` - specifies the health check node port (numeric port number) for the service. If not specified, `healthCheckNodePort` is -created by the service API backend with the allocated `nodePort`. It will use the -user-specified `nodePort` value if specified by the client. It only has an +created by the service API backend with the port allocated from range specified by `--service-node-port-range` in API server. It will use the +user-specified `healthCheckNodePort` value if specified by the client. It only has an effect when `type` is set to LoadBalancer and `externalTrafficPolicy` is set to Local. From 528cec311cf37020b26f9ac3fb74377ce335256b Mon Sep 17 00:00:00 2001 From: Fangyuan Li Date: Mon, 3 Feb 2020 10:01:13 -0800 Subject: [PATCH 2/2] Update content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md Co-Authored-By: Tim Bannister --- .../create-external-load-balancer.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md b/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md index 94cafb16d8022..720203d60d93e 100644 --- a/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md +++ b/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md @@ -128,8 +128,10 @@ load-spreading. Local preserves the client source IP and avoids a second hop for LoadBalancer and NodePort type services, but risks potentially imbalanced traffic spreading. * `service.spec.healthCheckNodePort` - specifies the health check node port -(numeric port number) for the service. If not specified, `healthCheckNodePort` is -created by the service API backend with the port allocated from range specified by `--service-node-port-range` in API server. It will use the +(numeric port number) for the service. If `healthCheckNodePort` isn't specified, +the service controller allocates a port from your cluster's NodePort range. You +can configure that range by setting an API server command line option, +`--service-node-port-range`. It will use the user-specified `healthCheckNodePort` value if specified by the client. It only has an effect when `type` is set to LoadBalancer and `externalTrafficPolicy` is set to Local.