h3. Feature Overview (aka. Goal Summary)  

This Feature adds support for EndPort in MultiNetworkPolicy for customers migrating VM instances to OpenShift Virtualization, and with a requirement to specify a port-range without having to individually specify each port separately. Without this Feature, customers will have issues migrating specific VMs to OpenShift Virtualization. It is currently supported with NetworkPolicy, but not yet with MultiNetworkPolicy.

Goals (aka. expected user outcomes)

A port range can be specified in MultiNetworkPolicy, instead of having to specify each port individually.

Requirements (aka. Acceptance Criteria):

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

• As a cluster admin I need to lock down which ports are exposed in my MultiNetworkPolicy specification. Large, individual port range specifications incur a great deal of processing overhead and are affecting my deployment, so I need to be able to specify a simple port range using something like:

      ports:
        - protocol: TCP
          port: 32000
          endPort: 32768

Reference Links:

• https://github.com/ovn-kubernetes/ovn-kubernetes/pull/4350
• https://github.com/k8snetworkplumbingwg/multi-networkpolicy/releases/tag/v1.0.1
• MultiNetworkPolicy product docs
• NetworkPolicy product docs

Questions to Answer (Optional):

Out of Scope

Background

Customer Considerations

Documentation Considerations

Interoperability Considerations