Skip to content

Commit 575aac0

Browse files
authored
Merge pull request #52293 from shiftstack/fix-lb-setting-kuryr
Bug OCPBUGS-2886: Add note about unnecessary load-balancer setting on CP
2 parents 0f1378a + c27d6a5 commit 575aac0

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

modules/installation-osp-setting-cloud-provider-options.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ $ vi openshift/manifests/cloud-provider-config.yaml
3131

3232
. Modify the options based on link:https://v1-18.docs.kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#cloud-conf[the `cloud.conf` specification].
3333
+
34-
Configuring Octavia for load balancing is a common case. For example:
34+
Configuring Octavia for load balancing is a common case for clusters that do not use Kuryr. For example:
3535
+
3636
[source,text]
3737
----
@@ -64,6 +64,11 @@ Prior to saving your changes, verify that the file is structured correctly. Clus
6464
====
6565
You must set the value of the `create-monitor` property to `True` if you use services that have the value of the `.spec.endpointTrafficPolicy` property set to `Local`. The OVN Octavia provider in {rh-openstack} 16.1 and 16.2 does not support health monitors. Therefore, services that have `ETP` parameter values set to `Local` might not respond when the `lb-provider` value is set to `"ovn"`.
6666
====
67+
+
68+
[IMPORTANT]
69+
====
70+
For installations that use Kuryr, Kuryr handles relevant services. There is no need to configure Octavia load balancing in the cloud provider.
71+
====
6772

6873
. Save the changes to the file and proceed with installation.
6974
+

0 commit comments

Comments
 (0)