1. Proposed title of this feature request

Ability to allow/specify multiple NodePort ranges in OpenShift or
Separate NodePort allocation range from the available range

2. What is the problem that your customer is facing?

By default, the NodePort range is between 30000-32768 and a random port is assigned from this range. The challenge is to assign static NodePort from within this range 7000-7999 specifically for one of their application and also have this default nodeport range 30000-32768 be available for assigning random ports

For customers, the requirement is for TCP mllp messages to use unique ports. Those ports must be fixed so that the customer does not have to change ports after an update, or when failing over to a DR site.

3. What is the nature and description of the request?

The request is for a second parameter that can be applied to network.config.io.cluster
The existing parameter serviceNodePortRange should specify the range of ports that are opened up externally, but a second parameter: serviceNodePortAllocationRange would allow the range for automatic allocation
Example
~~~
oc patch network.config.openshift.io cluster --type=merge -p
'{
"spec":

}'
~~~
This means that the range 7000-29999 is only available from static allocation, 30000-32768 would be dynamic (as it is already by default) (if a nodeport values is NOT specified in the service).
[NOTE: While it is possible to expand the current default node port range(30000-32767) but if we can have the ability to specify multiple nodeport ranges in OpenShift(not specifically 7000-29999 as mentioned in the example, but any two NodePort ranges, then it would be helpful to separate the workloads accordingly)]

4. Why does the customer need this? (List the business requirements here)

The business requirement is that we HAVE to open up the large NodePort range for our customers who use HL7 MLLP protocol and need a fixed port to communicate. By allowing the dynamic allocation from the same range as allowed ports, we run the risk of any service that does not specify a static port in its service, of grabbing a port from out fixed (static) range. Think of the way DHCP works is reserving a range of static IPs that are not part of the DHCP pool.

5. What is the business impact, if any, if this request will not be made available?

Major, as we have to use NodePorts, we would have to monitor for ports used an a continuous basis – and manually remove services that ‘take’ from the range we allocate to customers.

6. List any affected packages or components.
NodePort services