From 76ed14e8153b55f2d0d72b2f84aea1a4016b340f Mon Sep 17 00:00:00 2001 From: Maysa Macedo Date: Wed, 16 Sep 2020 15:59:30 +0200 Subject: [PATCH 1/2] Add note about restrictions with svc of LB type When Kuryr is used creation of Services with Load Balancer type are restricted to when a Router and External Connectivity exists on the Cluster. --- modules/installation-osp-kuryr-known-limitations.adoc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/modules/installation-osp-kuryr-known-limitations.adoc b/modules/installation-osp-kuryr-known-limitations.adoc index 9753bc0962b8..5ec655a2bbdd 100644 --- a/modules/installation-osp-kuryr-known-limitations.adoc +++ b/modules/installation-osp-kuryr-known-limitations.adoc @@ -11,7 +11,10 @@ Using {product-title} with Kuryr SDN has several known limitations. [id="openstack-general-limitations_{context}"] == {rh-openstack} general limitations -{product-title} with Kuryr SDN does not support NodePort services. +{product-title} with Kuryr SDN does not support NodePort services. Also, if +the machines subnet is not connected to a router or it's connected, but +the router has no external gateway set, Kuryr cannot create floating IPs +for LoadBalancer services. [discrete] [id="openstack-version-limitations_{context}"] @@ -80,4 +83,4 @@ API features, like UDP listeners. In this case, users must recreate their Servic If {product-title} detects a new Octavia version that supports UDP load balancing, it recreates the DNS Service automatically. The Service recreation ensures that the Service default supports UDP load balancing. The recreation causes the DNS Service approximately one minute of downtime. -==== \ No newline at end of file +==== From 39d4862cad854bcdfa23604d846367ace2ccd317 Mon Sep 17 00:00:00 2001 From: Max Bridges <50179998+maxwelldb@users.noreply.github.com> Date: Mon, 21 Sep 2020 09:38:53 -0400 Subject: [PATCH 2/2] Proposed edit --- modules/installation-osp-kuryr-known-limitations.adoc | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/modules/installation-osp-kuryr-known-limitations.adoc b/modules/installation-osp-kuryr-known-limitations.adoc index 5ec655a2bbdd..2500336ac805 100644 --- a/modules/installation-osp-kuryr-known-limitations.adoc +++ b/modules/installation-osp-kuryr-known-limitations.adoc @@ -11,10 +11,11 @@ Using {product-title} with Kuryr SDN has several known limitations. [id="openstack-general-limitations_{context}"] == {rh-openstack} general limitations -{product-title} with Kuryr SDN does not support NodePort services. Also, if -the machines subnet is not connected to a router or it's connected, but -the router has no external gateway set, Kuryr cannot create floating IPs -for LoadBalancer services. +{product-title} with Kuryr SDN does not support NodePort services. + +If the machines subnet is not connected to a router, or if the +subnet is connected, but the router has no external gateway set, +Kuryr cannot create floating IPs for LoadBalancer services. [discrete] [id="openstack-version-limitations_{context}"]