From 0b928b52b667acecec2bfc08266701aca0588bc4 Mon Sep 17 00:00:00 2001 From: Loic Blot Date: Thu, 27 Nov 2025 11:16:48 +0100 Subject: [PATCH 1/2] fix(service): add a link to band allocation blog post The service document talk about band but don't explain how it works in NodePort ranges. link it to the blog post explaining it --- content/en/docs/concepts/services-networking/service.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index 13eae552156e9..2e77cc1806926 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -535,6 +535,9 @@ To avoid this problem, the port range for NodePort services is divided into two Dynamic port assignment uses the upper band by default, and it may use the lower band once the upper band has been exhausted. Users can then allocate from the lower band with a lower risk of port collision. +For more details about how band is assigned, see the +[following blog post](/blog/2023/05/11/nodeport-dynamic-and-static-allocation/#how-can-you-avoid-nodeport-service-port-conflicts). + #### Custom IP address configuration for `type: NodePort` Services {#service-nodeport-custom-listen-address} You can set up nodes in your cluster to use a particular IP address for serving node port From cdc8303050345706a05d54e77efa719297c9618e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Blot?= Date: Mon, 1 Dec 2025 17:34:48 +0100 Subject: [PATCH 2/2] Update content/en/docs/concepts/services-networking/service.md Co-authored-by: Sean McGinnis --- 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 2e77cc1806926..8d0364a4948e9 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -535,7 +535,7 @@ To avoid this problem, the port range for NodePort services is divided into two Dynamic port assignment uses the upper band by default, and it may use the lower band once the upper band has been exhausted. Users can then allocate from the lower band with a lower risk of port collision. -For more details about how band is assigned, see the +For more details about how bands are assigned, see the [following blog post](/blog/2023/05/11/nodeport-dynamic-and-static-allocation/#how-can-you-avoid-nodeport-service-port-conflicts). #### Custom IP address configuration for `type: NodePort` Services {#service-nodeport-custom-listen-address}