From 2103a16c0fb410496bb8db27dd46777bc87ae786 Mon Sep 17 00:00:00 2001 From: "Paul \"TBBle\" Hampson" Date: Thu, 3 Feb 2022 02:31:43 +1100 Subject: [PATCH] Fix style nit-pick Co-authored-by: Tim Bannister Signed-off-by: Paul "TBBle" Hampson --- content/en/docs/concepts/services-networking/service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index 616aa02656..b4b01afc86 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -690,7 +690,7 @@ You can optionally disable node port allocation for a Service of `type=LoadBalan the field `spec.allocateLoadBalancerNodePorts` to `false`. This should only be used for load balancer implementations that route traffic directly to pods as opposed to using node ports. By default, `spec.allocateLoadBalancerNodePorts` is `true` and type LoadBalancer Services will continue to allocate node ports. If `spec.allocateLoadBalancerNodePorts` -is set to `false` on an existing Service with allocated node ports, those node ports will NOT be de-allocated automatically. +is set to `false` on an existing Service with allocated node ports, those node ports will **not** be de-allocated automatically. You must explicitly remove the `nodePorts` entry in every Service port to de-allocate those node ports. Your cluster must have the `ServiceLBNodePortControl` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)