RHDEVDOCS-5562: Creating content for Adding OpenShift Routes as a traffic manager for Argo Rollouts

Author: Dhruv-Soni11

argo_rollouts/using-argo-rollouts-for-progressive-deployment-delivery.adoc

@@ -36,6 +36,20 @@ include::modules/gitops-creating-rolloutmanager-custom-resource.adoc[leveloffset
 // Deleting a RolloutManager custom resource
 include::modules/gitops-deleting-rolloutmanager-custom-resource.adoc[leveloffset=+1]
 
+// Adding OpenShift Routes as a traffic manager for Argo Rollouts
+include::modules/con_adding-openshift-routes-as-a-traffic-manager-for-argo-rollouts.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+[id="additional-resources_argo_rollouts"]
+== Additional resources
+xref:../argo_rollouts/proc_installing-the-rollout-manager-plugin.adoc#proc_installing-the-rollout-manager-plugin[Create a RolloutManager custom resource]
+
+// Installing the rollout-manager Operator
+// include::modules/proc_installing-the-rollout-manager-operator.adoc[leveloffset=+2]
+
+// Installing the rollout-manager plugin
+include::modules/proc_installing-the-rollout-manager-plugin.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 [id="additional-resources_argo-rollouts-in-gitops"]
 == Additional resources

modules/con_adding-openshift-routes-as-a-traffic-manager-for-argo-rollouts.adoc

@@ -0,0 +1,23 @@
+:_mod-docs-content-type: CONCEPT
+
+[id="adding-openshift-routes-as-a-traffic-manager-for-argo-rollouts_{context}"]
+= Adding OpenShift Routes as a traffic manager for Argo Rollouts
+
+With traffic management, a user can modify the amount of traffic to direct it to various applications in a cluster environment. Users can choose to reduce or increase the traffic based on their requirements. 
+
+By enabling routes as traffic managers, a user using OpenShift in their environment ensures that new changes roll out adequately to all the cluster applications, enabling progressive delivery.
+
+You can use Openshift Route as a plugin and automatically install the plugin with the `RolloutManager` custom resource (CR).
+
+[discrete]
+== About OpenShift routes 
+
+An link:https://docs.openshift.com/container-platform/4.14/networking/routes/route-configuration.html[OpenShift Container Platform route] exposes a service at a host name, such as `www.example.com`, so that external clients can reach it by name.
+
+Routes can be either secured or unsecured. Secure routes provide the ability to use several types of TLS termination to serve certificates to the client.
+
+To install the rollout-manager, you must:
+
+* Create a RolloutManager custom resource
+* Install the rollout-manager plugin
+

modules/proc_installing-the-rollout-manager-operator.adoc

@@ -0,0 +1,42 @@
+:_mod-docs-content-type: PROCEDURE
+[id="installing-the-rollout-manager-operator_{context}"]
+= Installing the rollout-manager Operator
+
+You can install the `rollout-manager` Operator by defining the namespace and using the `Deploy` Operator.
+
+.Prerequisites
+
+* The `cluster-admin` cluster role must be assigned to the user.
+
+.Procedure
+
+. Defining the namespace - By default, the `rollout-manager` Operator is installed in the `argo-rollouts-manager-system` namespace. To modify the `rollout-manager` Operator, update the value of the `namespace` specified in the `config/default/kustomization.yaml` file.
+
+. Using the `Deploy` Operator - Deploy the `rollout-manager`:
++
+[source,terminal]
+----
+make deploy
+----
+
+. After the `rollout-manager` Operator is installed, you can use this Operator with the following configuration.
++
+[source,terminal]
+----
+apiVersion: argoproj.io/v1alpha1
+kind: RolloutManager
+metadata:
+ name: rollout-manager
+ labels:
+   example: basic
+spec: {}
+----
+
+. Add the following configuration to a YAML file:
++
+[source,terminal]
+----
+kubectl apply -f <path_to_file>
+----
++
+The rollout controller is created.

modules/proc_installing-the-rollout-manager-plugin.adoc

@@ -0,0 +1,72 @@
+:_mod-docs-content-type: PROCEDURE
+[id="installing-the-rollout-manager-plugin_{context}"]
+= Installing the rollout-manager plugin
+
+Once the rollout controller is created, you must install the rollout-manager plugin.
+
+.Prerequisites
+
+* The `cluster-admin` cluster role must be assigned to the user.
+
+.Procedure
+
+. Run the `yaml/rbac.yaml` file to add the role for running the required operations on the Openshift Route and build this plugin.
+
+. Save this plugin in your local system and mount it on the argo-rollouts container:
+
+.. Apply the rbac permissions:
++
+[source,terminal]
+----
+kubectl apply -f https://raw.githubusercontent.com/argoproj-labs/rollouts-plugin-trafficrouter-openshift/main/yaml/rbac.yaml
+----
+
+.. Optional: Update the ConfigMap argo-rollouts-config to provide an external location for the custom binary of the plugin.
++
+[source,terminal]
+----
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: argo-rollouts-config
+  namespace: argo-rollouts
+data:
+  trafficRouterPlugins: |-
+    - name: "argoproj-labs/openshift"
+      location: "file://CHANGE-ME/rollouts-trafficrouter-openshift/openshift-route-plugin"
+binaryData: {}
+----
+
+.. Create the CR/Rollout and add it into the operated services namespace:
++
+[source,terminal]
+----
+apiVersion: argoproj.io/v1alpha1
+kind: Rollout
+metadata:
+  name: rollouts-demo
+  namespace: rollouts-demo
+spec:
+    replicas: 2
+    selector:
+        matchLabels:
+        app.kubernetes.io/instance: rollouts-demo
+    strategy:
+        canary:
+        canaryService: canaryService
+        stableService: stableService
+        steps:
+            - setWeight: 30
+            - pause:
+                duration: 10
+        trafficRouting:
+            plugins:
+            argoproj-labs/openshift:
+                routes:
+                - rollouts-demo
+                namespace: rollouts-demo
+    workloadRef:
+        apiVersion: apps/v1
+        kind: Deployment
+        name: canary
+----