Feature Overview (aka. Goal Summary)  

Support direct ingress of traffic to pod IPs with OVN-Kubernetes. 

Goals (aka. expected user outcomes)

Currently, we do not support pod "direct" ingress (with or without routingviahost) in OVN-Kubernetes.  In support of customers using third-party LB solutions we will add support for this capability by enhancing our current Multiple External Gateways (MEG) support.

Currently targeted third-party solutions, in prioritized order:

1. [Broadcom VMware NSX Advanced Load Balancer / VMware AVI Load Balancer|https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/22-1.html]
2. F5 BIG-IP

Requirements (aka. Acceptance Criteria):

_**TBD*

 

*_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 an OpenShift project administrator, I want to be able to directly address podIPs in OVN-Kubernetes like I was able to do in the deprecated OpenShiftSDN CNI. 

Out of Scope

Background

• Red Hat internal Slack thread

Customer Considerations

Documentation Considerations

Interoperability Considerations

• F5 BIG-IP
• [Broadcom VMware NSX Advanced Load Balancer / VMware AVI Load Balancer|https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/22-1.html]
•