From 6b9bc4223306b3a33f26dc3dd2d9cb6c1c817703 Mon Sep 17 00:00:00 2001 From: xuzhenglun Date: Wed, 12 Apr 2023 19:15:26 +0800 Subject: [PATCH] fix typo for blog ServiceNodePortStaticSubrange --- .../_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md b/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md index fde6ed1c1d59e..78c2ca1d2fae7 100644 --- a/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md +++ b/content/en/blog/_posts/2023-05-11-nodeport-dynamic-and-static-allocation.md @@ -71,7 +71,7 @@ other Service; if so, creation of the `minio` Service will fail due to a node po ## How can you avoid NodePort Service port conflicts? Kubernetes 1.24 introduced changes for `type: ClusterIP` Services, dividing the CIDR range for cluster IP addresses into two blocks that use different allocation policies to [reduce the risk of conflicts](/docs/reference/networking/virtual-ips/#avoiding-collisions). -In Kubernetes 1.27, as an alpha feature, you can adopt a similar policy for `type: NodePort` Servies. +In Kubernetes 1.27, as an alpha feature, you can adopt a similar policy for `type: NodePort` Services. You can enable a new [feature gate](/docs/reference/command-line-tools-reference/feature-gates/) `ServiceNodePortStaticSubrange`. Turning this on allows you to use a different port allocation strategy for `type: NodePort` Services, and reduce the risk of collision.