OpenStack: Update LB limitations for 4.14

dulek · dulek · commit 1bc7f041cceb · 2023-11-06T16:43:51.000+01:00
In 4.14 `.spec.loadBalancerSourceRanges` are supported with OVN Octavia
Provider thanks to OSASINFRA-3067. This commit removes the mention of
this not being supported from the docs.

Moreover docs are updated to explain that HTTP health monitors are not
supported by the OVN Octavia Provider and the consequences behind this.
diff --git a/modules/nw-osp-loadbalancer-etp-local.adoc b/modules/nw-osp-loadbalancer-etp-local.adoc
@@ -11,4 +11,4 @@ Having the `ETP` option set to `Local` requires that health monitors be created
 
 In {rh-openstack} 16.2, the OVN Octavia provider does not support health monitors. Therefore, setting the ETP to local is unsupported.
 
-In {rh-openstack} 16.2, the Amphora Octavia provider does not support HTTP monitors on UDP pools. As a result, UDP load balancer services have `UDP-CONNECT` monitors created instead. Due to implementation details, this configuration only functions properly with the OVN-Kubernetes CNI plugin. When the OpenShift SDN CNI plugin is used, the UDP services alive nodes are detected unreliably.
+In {rh-openstack} 16.2, the Amphora Octavia provider does not support HTTP monitors on UDP pools. As a result, UDP load balancer services have `UDP-CONNECT` monitors created instead. Due to implementation details, this configuration only functions properly with the OVN-Kubernetes CNI plugin. When the OpenShift SDN CNI plugin is used, the UDP services alive nodes are detected unreliably. This issue also affects the OVN Octavia provider in any {rh-openstack} version because the driver does not support HTTP health monitors.
diff --git a/modules/nw-osp-loadbalancer-source-ranges.adoc b/modules/nw-osp-loadbalancer-source-ranges.adoc
diff --git a/networking/load-balancing-openstack.adoc b/networking/load-balancing-openstack.adoc
@@ -8,7 +8,6 @@ toc::[]
 
 include::modules/nw-osp-loadbalancer-limitations.adoc[leveloffset=+1]
 include::modules/nw-osp-loadbalancer-etp-local.adoc[leveloffset=+2]
-include::modules/nw-osp-loadbalancer-source-ranges.adoc[leveloffset=+2]
 include::modules/installation-osp-kuryr-octavia-upgrade.adoc[leveloffset=+1]
 include::modules/installation-osp-api-octavia.adoc[leveloffset=+1]
 include::modules/installation-osp-api-scaling.adoc[leveloffset=+2]

Original file line number	Diff line number	Diff line change
@@ -11,4 +11,4 @@ Having the `ETP` option set to `Local` requires that health monitors be created
`11`	`11`
`12`	`12`	`In {rh-openstack} 16.2, the OVN Octavia provider does not support health monitors. Therefore, setting the ETP to local is unsupported.`
`13`	`13`
`14`		-In {rh-openstack} 16.2, the Amphora Octavia provider does not support HTTP monitors on UDP pools. As a result, UDP load balancer services have `UDP-CONNECT` monitors created instead. Due to implementation details, this configuration only functions properly with the OVN-Kubernetes CNI plugin. When the OpenShift SDN CNI plugin is used, the UDP services alive nodes are detected unreliably.
	`14`	+In {rh-openstack} 16.2, the Amphora Octavia provider does not support HTTP monitors on UDP pools. As a result, UDP load balancer services have `UDP-CONNECT` monitors created instead. Due to implementation details, this configuration only functions properly with the OVN-Kubernetes CNI plugin. When the OpenShift SDN CNI plugin is used, the UDP services alive nodes are detected unreliably. This issue also affects the OVN Octavia provider in any {rh-openstack} version because the driver does not support HTTP health monitors.