Feature Overview (aka. Goal Summary)  

Support the ability to create arbitrary interfaces.

It sounds like to me that they need the ability to create the arbitrary interfaces, while whereabouts can assign the arbitrary static IPs, it doesn't let you create the dummy interfaces.

Goals (aka. expected user outcomes)

Provide support for the ability to create arbitrary local interfaces, for example using a "dummy" CNI plug-in, for assignation of custom fixed IPs to be used for routing between application peers.

Requirements (aka. Acceptance Criteria):

• Primarily needs documentation and QE
   

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):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Out of Scope

Background

Customer needs stable, fixed IPs (agnostic of cluster) for routing between application peers. These IPs would be configured on a set of interfaces created using, for example, a Dummy CNI plug-in and traffic would be routed via the pod's configured IP. Routes will be managed externally. This solution will only require the static IPAM features of CNI. Customer can provide generic example of the configuration they have been testing with.

The already-supported whereabouts CNI can assign arbitrary static IPs, but it doesn't let you create the dummy interfaces.

Customer Considerations

• The customer requires this in early 2024 for their OCP 4.14 deployment
• A Support Exception will be filed for earlier (than feature release) support

Documentation Considerations

Interoperability Considerations