Merge pull request #59054 from xenolinux/migrate-albo-examples-v1

OSDOCS#5794: Migrate all the AWS Load Balancer Operator examples to versio "v1"

Author: mburke5678

modules/adding-tls-termination.adoc

@@ -18,9 +18,8 @@ You can route the traffic for the domain to pods of a service and add TLS termin
 +
 [source,yaml]
 ----
-apiVersion: networking.k8s.io/v1
+apiVersion: networking.olm.openshift.io/v1
 kind: AWSLoadBalancerController
-group: networking.olm.openshift.io/v1alpha1 <1>
 metadata:
   name: cluster <2>
 spec:

modules/configuring-albo-on-sts-cluster-predefined-credentials.adoc

@@ -56,7 +56,7 @@ $ oc -n aws-load-balancer-operator get secret aws-load-balancer-controller-manua
 +
 [source,yaml]
 ----
-apiVersion: networking.olm.openshift.io/v1alpha1
+apiVersion: networking.olm.openshift.io/v1
 kind: AWSLoadBalancerController <1>
 metadata:
   name: cluster <2>

modules/creating-instance-aws-load-balancer-controller.adoc

@@ -19,15 +19,15 @@ You can install only a single instance of the `aws-load-balancer-controller` in
 +
 [source,yaml]
 ----
-apiVersion: networking.olm.openshift.io/v1alpha1
+apiVersion: networking.olm.openshift.io/v1
 kind: AWSLoadBalancerController <1>
 metadata:
   name: cluster <2>
 spec:
   subnetTagging: Auto <3>
   additionalResourceTags: <4>
-    example.org/cost-center: 5113232
-    example.org/security-scope: staging
+  - key: example.org/security-scope
+    value: staging
   ingressClass: cloud <5>
   config:
     replicas: 2 <6>

modules/installing-aws-load-balancer-operator.adoc

@@ -22,7 +22,7 @@ You can install the AWS Load Balancer Operator from the OperatorHub by using the
 . Follow the instructions to prepare the Operator for installation.
 . On the *AWS Load Balancer Operator* page, click *Install*.
 . On the *Install Operator* page, select the following options:
-.. *Update the channel* as *stable-v0*.
+.. *Update the channel* as *stable-v1*.
 .. *Installation mode* as *A specific namespace on the cluster*.
 .. *Installed Namespace* as `aws-load-balancer-operator`. If the `aws-load-balancer-operator` namespace does not exist, it gets created during the Operator installation.
 .. Select *Update approval* as *Automatic* or *Manual*. By default, the *Update approval* is set to *Automatic*. If you select automatic updates, the Operator Lifecycle Manager (OLM) automatically upgrades the running instance of your Operator without any intervention. If you select manual updates, the OLM creates an update request. As a cluster administrator, you must then manually approve that update request to update the Operator updated to the new version.