Chapter 1. Using Argo Rollouts for progressive deployment delivery

Procedure

1. Log in to the OpenShift Container Platform web console as a cluster administrator.
2. In the Administrator perspective, click Operators Installed Operators.
3. Create or select the project where you want to create and configure a RolloutManager custom resource (CR) from the Project drop-down menu.
4. Select OpenShift GitOps Operator from the installed operators.
5. In the Details tab, under the Provided APIs section, click Create instance in the RolloutManager pane.

6. On the Create RolloutManager page, select the YAML view and use the default YAML or edit it according to your requirements:

   Example: RolloutManager CR

   apiVersion: argoproj.io/v1alpha1
   kind: RolloutManager
   metadata:
     name: argo-rollout
     labels:
       example: basic
   spec: {}

7. Click Create.
8. In the RolloutManager tab, under the RolloutManagers section, verify that the Status field of the RolloutManager instance shows as Phase: Available.

9. In the left navigation pane, verify the creation of the namespace-scoped supporting resources:

   • Click Workloads Deployments to verify that the argo-rollouts deployment is available with the Status showing as 1 of 1 pods running.
   • Click Workloads Secrets to verify that the argo-rollouts-notification-secret secret is available.
   • Click Networking Services to verify that the argo-rollouts-metrics service is available.
   • Click User Management Roles to verify that the argo-rollouts role and argo-rollouts-aggregate-to-admin, argo-rollouts-aggregate-to-edit, and argo-rollouts-aggregate-to-view cluster roles are available.
   • Click User Management RoleBindings to verify that the argo-rollouts role binding is available.

Procedure

1. Log in to the OpenShift Container Platform web console as a cluster administrator.
2. In the Administrator perspective, click Operators Installed Operators.
3. Click the Project drop-down menu and select the project that contains the RolloutManager CR.
4. Select OpenShift GitOps Operator from the installed operators.
5. Click the RolloutManager tab to find RolloutManager instances under the RolloutManagers section.
6. Click the instance.
7. Click Actions Delete RolloutManager from the drop-down menu, and click Delete to confirm in the dialog box.
8. In the RolloutManager tab, under the RolloutManagers section, verify that the RolloutManager instance is not available anymore.

9. In the left navigation pane, verify the deletion of the namespace-scoped supporting resources:

   • Click Workloads Deployments to verify that the argo-rollouts deployment is deleted.
   • Click Workloads Secrets to verify that the argo-rollouts-notification-secret secret is deleted.
   • Click Networking Services to verify that the argo-rollouts-metrics service is deleted.
   • Click User Management Roles to verify that the argo-rollouts role and argo-rollouts-aggregate-to-admin, argo-rollouts-aggregate-to-edit, and argo-rollouts-aggregate-to-view cluster roles are deleted.
   • Click User Management RoleBindings to verify that the argo-rollouts role binding is deleted.