Merge pull request #46191 from ahardin-rh/BZ-2026192

Bug 2026192, noted new limitation of OVN environment

Author: ahardin-rh

modules/nw-ovn-kuberentes-limitations.adoc

@@ -10,6 +10,8 @@ The OVN-Kubernetes Container Network Interface (CNI) cluster network provider ha
 * OVN-Kubernetes does not support setting the internal traffic policy for a Kubernetes service to `local`.
 This limitation can affect network communication to your application when you add a service of type `ClusterIP`, `LoadBalancer`, `NodePort`, or add a service with an external IP.
 
+* The `sessionAffinityConfig.clientIP.timeoutSeconds` service has no effect in an OpenShift OVN environment, but does in an OpenShift SDN environment. This incompatibility can make it difficult for users to migrate from OpenShift SDN to OVN.
+
 // The foll limitation is also recorded in the installation section.
 * For clusters configured for dual-stack networking, both IPv4 and IPv6 traffic must use the same network interface as the default gateway.
 If this requirement is not met, pods on the host in the `ovnkube-node` daemon set enter the `CrashLoopBackOff` state.
@@ -23,4 +25,3 @@ F1006 16:09:50.985939   60651 ovnkube.go:130] multiple gateway interfaces detect
 ----
 +
 The only resolution is to reconfigure the host networking so that both IP families use the same network interface for the default gateway.
-