From ffa8890393fd3afa32eb676089238869420bcd84 Mon Sep 17 00:00:00 2001 From: Steven Smith Date: Wed, 8 Jun 2022 16:31:38 -0400 Subject: [PATCH] Removes OVN K internal traffic policy limitation --- modules/nw-ovn-kuberentes-limitations.adoc | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/modules/nw-ovn-kuberentes-limitations.adoc b/modules/nw-ovn-kuberentes-limitations.adoc index a43bbdf42a..1e101ec7ea 100644 --- a/modules/nw-ovn-kuberentes-limitations.adoc +++ b/modules/nw-ovn-kuberentes-limitations.adoc @@ -5,10 +5,7 @@ [id="nw-ovn-kubernetes-limitations_{context}"] = OVN-Kubernetes limitations -The OVN-Kubernetes Container Network Interface (CNI) cluster network provider has the following limitations: - -* 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 OVN-Kubernetes Container Network Interface (CNI) cluster network provider has the following limitation: // 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. @@ -23,4 +20,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. -