Fix MetalLB YAML examples

This commit also updates MetalLB BGPPeer to API version v1beta2,
encouraging users to use latest supported API version.

Signed-off-by: Carlos Goncalves <[email protected]>

Author: cgoncalves

modules/nw-metallb-advertise-address-pool-with-bgp-advanced.adoc

@@ -56,11 +56,11 @@ metadata:
   namespace: metallb-system
 spec:
   ipAddressPools:
-   - doc-example-bgp-adv
-  - communities:
+    - doc-example-bgp-adv
+  communities:
     - 65535:65282
-    aggregationLength: 32
-    localPref: 100
+  aggregationLength: 32
+  localPref: 100
 ----
 
 .. Apply the configuration:
@@ -81,11 +81,11 @@ metadata:
   namespace: metallb-system
 spec:
   ipAddressPools:
-   - doc-example-bgp-adv
-  - communities:
+    - doc-example-bgp-adv
+  communities:
     - 8000:800
-    aggregationLength: 30
-    aggregationLengthV6: 124
+  aggregationLength: 30
+  aggregationLengthV6: 124
 ----
 
 .. Apply the configuration:

modules/nw-metallb-configure-bgppeer.adoc

@@ -22,7 +22,7 @@ As a cluster administrator, you can add a BGP peer custom resource to exchange r
 +
 [source,yaml]
 ----
-apiVersion: metallb.io/v1beta1
+apiVersion: metallb.io/v1beta2
 kind: BGPPeer
 metadata:
   namespace: metallb-system

modules/nw-metallb-configure-community-bgp-advertisement.adoc

@@ -64,7 +64,7 @@ spec:
 +
 [source,yaml]
 ----
-apiVersion: metallb.io/v1beta1
+apiVersion: metallb.io/v1beta2
 kind: BGPPeer
 metadata:
   namespace: metallb-system
@@ -110,4 +110,4 @@ spec:
 [source,terminal]
 ----
 $ oc apply -f bgpadvertisement.yaml
-----
+----

modules/nw-metallb-configure-specificpools-to-bgppeer.adoc

@@ -73,7 +73,7 @@ $ oc apply -f ipaddresspool2.yaml
 +
 [source,yaml]
 ----
-apiVersion: metallb.io/v1beta1
+apiVersion: metallb.io/v1beta2
 kind: BGPPeer
 metadata:
   namespace: metallb-system
@@ -98,7 +98,7 @@ $ oc apply -f bgppeer1.yaml
 +
 [source,yaml]
 ----
-apiVersion: metallb.io/v1beta1
+apiVersion: metallb.io/v1beta2
 kind: BGPPeer
 metadata:
   namespace: metallb-system
@@ -130,13 +130,13 @@ metadata:
   namespace: metallb-system
 spec:
   ipAddressPools:
-  - pool1
+    - pool1
   peers:
     - peer1
-  - communities:
-      - 65535:65282
- aggregationLength: 32
- aggregationLengthV6: 128
+  communities:
+    - 65535:65282
+  aggregationLength: 32
+  aggregationLengthV6: 128
   localPref: 100
 ----
 
@@ -160,13 +160,13 @@ metadata:
   namespace: metallb-system
 spec:
   ipAddressPools:
-  - pool2
+    - pool2
   peers:
     - peer2
-  - communities:
-      - 65535:65282
- aggregationLength: 32
- aggregationLengthV6: 128
+  communities:
+    - 65535:65282
+  aggregationLength: 32
+  aggregationLengthV6: 128
   localPref: 100
 ----
 

modules/nw-metallb-example-bgppeer.adoc

@@ -13,7 +13,7 @@ You can specify the node selectors field to control which nodes can connect to a
 
 [source,yaml]
 ----
-apiVersion: metallb.io/v1beta1
+apiVersion: metallb.io/v1beta2
 kind: BGPPeer
 metadata:
   name: doc-example-nodesel
@@ -37,7 +37,7 @@ BFD compliments BGP by providing more rapid detection of communication failures
 
 [source,yaml]
 ----
-apiVersion: metallb.io/v1beta1
+apiVersion: metallb.io/v1beta2
 kind: BGPPeer
 metadata:
   name: doc-example-peer-bfd
@@ -57,7 +57,7 @@ To support dual-stack networking, add one BGP peer custom resource for IPv4 and
 
 [source,yaml]
 ----
-apiVersion: metallb.io/v1beta1
+apiVersion: metallb.io/v1beta2
 kind: BGPPeer
 metadata:
   name: doc-example-dual-stack-ipv4
@@ -67,7 +67,7 @@ spec:
   peerASN: 64500
   myASN: 64500
 ---
-apiVersion: metallb.io/v1beta1
+apiVersion: metallb.io/v1beta2
 kind: BGPPeer
 metadata:
   name: doc-example-dual-stack-ipv6