-
Feature Request
-
Resolution: Done-Errata
-
Critical
-
None
-
None
-
13
-
False
-
-
False
-
-
-
FDP 24.D, FDP 24.E, FDP 24.F
- Proposed title of this feature request
Multiple SNATs per logical IP
2. What is the nature and description of the request?
Background
We want to use an OVN-Kubernetes CRD Egress IP depending on a destination IP for a given pod. Today, we only allow one Egress IP (EIP) per pod.
This request is looking for OVN support so that a pod may have multiple EIPs and the EIP is chosen based on the destination.
For example, for a given pod logical IP, if it tries to talk to destination IP X, it gets EIP A, and if it tries to talk to destination IP Y, it gets EIP B, otherwise it gets SNAT'd to a node IP.
Today, it seems there is no way to have multiple entries in the NAT table with equal logical_ip.
ovn-nbctl: a NAT with this type (snat), logical_ip (10.244.2.3) already exists
3. Why does the customer need this? (List the business requirements here)
They wish an application may have a defined IP for different k8 cluster external services it talks to. This application will talk to multiple external services and each requires a static IP.
4. List any affected packages or components.
OVN 23.09
- is blocked by
-
FDP-400 [OVN] Direct access to SNATed Network is not SNATed properly.
- Closed
- links to
-
RHBA-2024:138790 ovn24.09 bug fix and enhancement update
- mentioned on