From f4856917bf223b4b59cdecf189732c39958951be Mon Sep 17 00:00:00 2001 From: Max Bridges Date: Mon, 13 Jul 2020 09:27:31 -0400 Subject: [PATCH] Remove outdated Kuryr + Octavia compat notes This change addresses openshift-docs issue 23711 https://github.com/openshift/openshift-docs/issues/23711 --- .../installation-osp-kuryr-known-limitations.adoc | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/modules/installation-osp-kuryr-known-limitations.adoc b/modules/installation-osp-kuryr-known-limitations.adoc index 5bd990e2d508..9753bc0962b8 100644 --- a/modules/installation-osp-kuryr-known-limitations.adoc +++ b/modules/installation-osp-kuryr-known-limitations.adoc @@ -34,23 +34,13 @@ OpenShift UDP services are not supported. same port. Services that expose the same port to different protocols, like TCP and UDP, are not supported. -[IMPORTANT] -==== -The OVN Octavia driver does not support listeners that use different protocols on -any {rh-openstack} version. -==== - [discrete] [id="openstack-go-limitations_{context}"] == {rh-openstack} environment limitations There are limitations when using Kuryr SDN that depend on your deployment environment. -Because of Octavia's lack of support for the UDP protocol and multiple listeners, Kuryr forces Pods to use TCP -for DNS resolution if: - -* The {rh-openstack} version is earlier than 16 -* The OVN Octavia driver is used +Because of Octavia's lack of support for the UDP protocol and multiple listeners, if the {rh-openstack} version is earlier than 16, Kuryr forces Pods to use TCP for DNS resolution. In Go versions 1.12 and earlier, applications that are compiled with CGO support disabled use UDP only. In this case, the native Go resolver does not recognize the `use-vc` option in `resolv.conf`, which controls whether TCP is forced for DNS resolution.