Chapter 9. Using a cluster-scoped Argo Rollouts instance to manage rollout resources
By default, Argo Rollouts supports the cluster-scoped mode of installation for Argo Rollouts custom resources (CRs). This mode of installation uses the
CLUSTER_SCOPED_ARGO_ROLLOUTS_NAMESPACES
To manage Argo Rollouts resources, after you install the Red Hat OpenShift GitOps Operator on the cluster, you can create and configure a
RolloutManager
Subscription
CLUSTER_SCOPED_ARGO_ROLLOUTS_NAMESPACES
spec
9.1. Prerequisites Copy linkLink copied to clipboard!
- You have logged in to the OpenShift Container Platform cluster as an administrator.
- You have installed the Red Hat OpenShift GitOps Operator on your OpenShift Container Platform cluster.
-
You have created a custom resource.
RolloutManager
9.2. Configuring a cluster-scoped Argo Rollouts instance to manage rollout resources Copy linkLink copied to clipboard!
To configure a cluster-scoped Argo Rollouts instance for managing rollout resources, add the
CLUSTER_SCOPED_ARGO_ROLLOUTS_NAMESPACES
Subscription
CLUSTER_SCOPED_ARGO_ROLLOUTS_NAMESPACES
openshift-gitops
You can only create a cluster-scoped Argo Rollouts instance if the
NAMESPACE_SCOPED_ARGO_ROLLOUTS
false
NAMESPACE_SCOPED_ARGO_ROLLOUTS
false
Procedure
-
In the Administrator perspective of the web console, navigate to Operators
Installed Operators Red Hat OpenShift GitOps Subscription. - Click the Actions list and then click Edit Subscription.
On the openshift-gitops-operator Subscription details page, under the YAML tab, edit the
YAML file by adding the namespace of the Argo CD instance to theSubscriptionenvironment variable in theCLUSTER_SCOPED_ARGO_ROLLOUTS_NAMESPACESsection:specExample configuring the
CLUSTER_SCOPED_ARGO_ROLLOUTS_NAMESPACESenvironment variable:apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: openshift-gitops-operator spec: config: env: - name: NAMESPACE_SCOPED_ARGO_ROLLOUTS value: 'false' - name: CLUSTER_SCOPED_ARGO_ROLLOUTS_NAMESPACES value: <list_of_namespaces_in_the_cluster-scoped_Argo_CD_instances> ...where:
- spec.config.env.value ('false')
-
Specify this value to enable or disable the cluster-scoped installation. Set the value to
'false'to enable cluster-scoped installation. Set to'true'to enable namespace-scoped installation. If this value is empty, the operator defaults tofalse. - spec.config.env.value (list_of_namespaces)
-
Specifies a comma-separated list of namespaces that can host a cluster-scoped Argo Rollouts instance, for example
test-123-cluster-scoped,test-456-cluster-scoped.
- Click Save and Reload.