Chapter 8. Enabling high availability support for Argo Rollouts

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 CR from the Project drop-down menu.
4. Select Red Hat OpenShift GitOps 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 edit the YAML.

   Example enabling the ha field in the RolloutManager CR

   apiVersion: argoproj.io/v1alpha1
   kind: RolloutManager
   metadata:
     name: argo-rollouts
     namespace: openshift-gitops
   spec:
     ha:
       enabled: true 

   1

   Copy to Clipboard Toggle word wrap

   1

   Specifies whether high availability is enabled or not. If the value is set to true, high availability is enabled.

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

9. Verify the status of the Rollouts deployment by completing the following steps:

   1. In the Administrator perspective, click Workloads Deployments.
   2. Click the argo-rollouts deployment.
   3. Click the Details tab and confirm that the number of replicas in the Rollouts deployment is now set to 2.

   4. Click the YAML tab and confirm that the following configuration is displayed:

      Example Argo Rollouts deployment configuration file

      kind: Deployment
      metadata:
        name: argo-rollouts
        namespace: openshift-gitops
      spec:
        replicas: 2 

      1

      
        selector:
          matchLabels:
            app.kubernetes.io/name: argo-rollouts
        template:
          metadata:
            creationTimestamp: null
            labels:
              app.kubernetes.io/name: argo-rollouts
          spec:
            containers:
                args:
                  - '--leader-elect'
                  - 'true' 

      2

      Copy to Clipboard Toggle word wrap

      1

      Specifies the number of pods.

      2

      Specifies that the --leader-elect=true flag is passed to the Rollouts deployment. Although this flag is set to true by default, explicitly setting it ensures that leader election remains consistently enforced.