+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.
0 commit comments