Skip to content

Commit ff93fd0

Browse files
committed
add docs in service concepts
1 parent 547e2be commit ff93fd0

File tree

1 file changed

+7
-0
lines changed
  • content/en/docs/concepts/services-networking

1 file changed

+7
-0
lines changed

content/en/docs/concepts/services-networking/service.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -586,6 +586,13 @@ spec:
586586
nodePort: 30007
587587
```
588588
589+
#### Reserve Nodeport Ranges to avoid collisions when port assigning
590+
591+
{{< feature-state for_k8s_version="v1.27" state="alpha" >}}
592+
593+
NodePort's port assignment policy exists for both dynamic auto-assignment and manual assignment by the user. When a user wishes to create a NodePort for a specific port, it may conflict with an already automatically assigned port. To solve this problem, you can turning featuregate `ServiceNodePortStaticSubrange`, which allows you to use a different port allocation strategy for NodePort-type Services, and reducing the risk of collision. The port range for `NodePort` will be divided, and dynamic port assignment will use the upper band by default, once this has been exhausted it will use the lower range. This will allow users to use static allocations on the lower band with a low risk of collision.
594+
595+
589596
#### Custom IP address configuration for `type: NodePort` Services {#service-nodeport-custom-listen-address}
590597

591598
You can set up nodes in your cluster to use a particular IP address for serving node port

0 commit comments

Comments
 (0)