Skip to content

[enterprise-4.6] Remove outdated Kuryr + Octavia compatibility notes #23879

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maxwelldb merged 1 commit into from
Jul 16, 2020
Merged

[enterprise-4.6] Remove outdated Kuryr + Octavia compatibility notes #23879

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 1 addition & 11 deletions modules/installation-osp-kuryr-known-limitations.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down