From ce726fb02974ee67a08ea9faccd8fa44592dc911 Mon Sep 17 00:00:00 2001
From: Brendan Daly <bdaly@redhat.com>
Date: Fri, 3 Jan 2025 14:26:24 +0000
Subject: [PATCH] OCPBUGS-42984:updating parameter alignment

---
 modules/nw-osp-configuring-external-load-balancer.adoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/modules/nw-osp-configuring-external-load-balancer.adoc b/modules/nw-osp-configuring-external-load-balancer.adoc
index 12bd91e6cb..26f74c2b84 100644
--- a/modules/nw-osp-configuring-external-load-balancer.adoc
+++ b/modules/nw-osp-configuring-external-load-balancer.adoc
@@ -345,10 +345,10 @@ ifdef::vsphere[]
 endif::vsphere[]
     loadBalancer:
       type: UserManaged <1>
-      apiVIPs:
-      - <api_ip> <2>
-      ingressVIPs:
-      - <ingress_ip> <3>
+    apiVIPs:
+    - <api_ip> <2>
+    ingressVIPs:
+    - <ingress_ip> <3>
 # ...
 ----
 <1> Set `UserManaged` for the `type` parameter to specify a user-managed load balancer for your cluster. The parameter defaults to `OpenShiftManagedDefault`, which denotes the default internal load balancer. For services defined in an `openshift-kni-infra` namespace, a user-managed load balancer can deploy the `coredns` service to pods in your cluster but ignores `keepalived` and `haproxy` services.