Chapter 6. Enabling support for a namespace-scoped Argo Rollouts installation

Procedure

1. In the Administrator perspective of the web console, go to Administration CustomResourceDefinitions.
2. Search for Subscription and click the Subscription CRD.
3. Click the Instances tab and then click the openshift-gitops-operator subscription.

4. Click the YAML tab and edit the YAML file.

   1. Specify the NAMESPACE_SCOPED_ARGO_ROLLOUTS environment variable, with the value set to true in the .spec.config.env property.

      Example of configuring the namespace-scoped Argo Rollouts installation

      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: openshift-gitops-operator
      spec:
        # (...)
        config:
          env:
            - name: NAMESPACE_SCOPED_ARGO_ROLLOUTS
              value: 'true' 

      1

      Copy to Clipboard Toggle word wrap

      1

      The value set to 'true' enables namespace-scoped installation. If the value is set to 'false' or not specified the installation defaults to cluster-scoped mode.

   2. Click Save.

      The Red Hat OpenShift GitOps Operator facilitates the reconciliation of the Argo Rollouts custom resource within a namespace-scoped installation.

5. Verify that the Red Hat OpenShift GitOps Operator has enabled the namespace-scoped Argo Rollouts installation by viewing the logs of the GitOps container:

   1. In the Administrator perspective of the web console, go to Workloads Pods.
   2. Click the openshift-gitops-operator-controller-manager pod, and then click the Logs tab.
   3. Look for the following log statement: Running in namespaced-scoped mode. This statement indicates that the Red Hat OpenShift GitOps Operator has enabled the namespace-scoped Argo Rollouts installation.

6. Create a RolloutManager resource to complete the namespace-scoped Argo Rollouts installation:

   1. Go to Operators Installed Operators Red Hat OpenShift GitOps, and click the RolloutManager tab.
   2. Click Create RolloutManager.

   3. Select YAML view and enter the following snippet:

      Example RolloutManager CR for a namespace-scoped Argo Rollouts installation

      apiVersion: argoproj.io/v1alpha1
      kind: RolloutManager
      metadata:
        name: rollout-manager
        namespace: my-application 

      1

      
      spec:
        namespaceScoped: true

      Copy to Clipboard Toggle word wrap

      1

      Specify the name of the project where you want to install the namespace-scoped Argo Rollouts instance.

   4. Click Create.

      After the RolloutManager CR is created, Red Hat OpenShift GitOps begins to install the namespace-scoped Argo Rollouts instance into the selected namespace.

7. Verify that the namespace-scoped installation is successful.

   1. In the RolloutManager tab, under the RolloutManagers section, ensure that the Status field of the RolloutManager instance is Phase: Available.

   2. Examine the following output in the YAML tab under the RolloutManagers section to ensure that the installation is successful:

      Example of namespace-scoped Argo Rollouts installation YAML file

      spec:
        namespaceScoped: true
      status:
        conditions:
          lastTransitionTime: '2024-07-10T14:20:5z`
          message: ''
          reason: Success
          status: 'True' 

      1

      
          type: 'Reconciled'
        phase: Available
        rolloutController: Available

      Copy to Clipboard Toggle word wrap

      1

      This status indicates that the namespace-scoped Argo Rollouts installation is enabled successfully.

      If you try to install a namespace-specific Argo Rollouts instance while a cluster-scoped installation already exists on the cluster, an error message is displayed:

      Example of an incorrect installation with an error message

      spec:
        namespaceScoped: true
      status:
        conditions:
         lastTransitionTime: '2024-07-10T14:10:7z`
         message: 'when Subscription has environment variable NAMESPACE_SCOPED_ARGO_ROLLOUTS set to False, there may not exist any namespace-scoped RolloutManagers: only a single cluster-scoped RolloutManager is supported'
         reason: InvalidRolloutManagerScope
         status: 'False' 

      1

      
         type: 'Reconciled'
        phase: Failure
        rolloutController: Failure

      Copy to Clipboard Toggle word wrap

      1

      This status indicates that the namespace-scoped Argo Rollouts installation is not enabled successfully. The installation defaults to cluster-scoped mode.