You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was a previous bug where when an egress packet would be SNAT'ed to
the node IP, using a nodeport source port, it would cause reply traffic
to get DNAT'ed to the nodeport load balancer. This happened because the
egress connections were not conntracked correctly.
This was fixed via:
https://issues.redhat.com/browse/OCPBUGS-25889https://issues.redhat.com/browse/FDP-291
However, that fix was not hardware offloadable. The ideal fix here would
be to always commit to conntrack and have it be HW offloadable. Until we
have a better solution, we can configure the port range for OVN to use
on its SNAT. This applies to all SNATs for traffic that enters the local
host or leaves the host.
The new config option --ephemeral-port-range "<minPort>-<maxPort>" can
be used to specify the port range to use with OVN. If not provided, this
value will be automatically derived from the ephemeral port range in
/proc/sys/net/ipv4/ip_local_port_range, which is typically set already
to avoid nodeport range conflicts.
Signed-off-by: Tim Rozet <[email protected]>
0 commit comments