Bug OCPBUGS-2886: Add note about uncessary load-balancer settting on CP

When using Kuryr the OpenShift Services are already handled by Kuryr
consequently Octavia and not by the cloud provider. The changes the user
might attempt to do in the LoadBalancer section will not have any effect
in the load-balancers created by Kuryr. This commit fixes the issue by
stating that config section is only valid for installations without Kuryr
and the reasoning behind it.

Co-authored-by: Max Bridges <[email protected]>

Author: MaysaMacedo

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

@@ -31,7 +31,7 @@ $ vi openshift/manifests/cloud-provider-config.yaml
 
 . Modify the options based on link:https://v1-18.docs.kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#cloud-conf[the `cloud.conf` specification].
 +
-Configuring Octavia for load balancing is a common case. For example:
+Configuring Octavia for load balancing is a common case for clusters that do not use Kuryr. For example:
 +
 [source,text]
 ----
@@ -64,6 +64,11 @@ Prior to saving your changes, verify that the file is structured correctly. Clus
 ====
 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"`.
 ====
++
+[IMPORTANT]
+====
+For installations that use Kuryr, Kuryr handles relevant services. There is no need to configure Octavia load balancing in the cloud provider.
+====
 
 . Save the changes to the file and proceed with installation.
 +