Skip to content

acm-setup role

This role performs the Advanced Cluster Management (ACM) post-installation tasks that include:

  1. Installation of multicluster-engine and OADP operators
  2. Creation of a multicluster engine
  3. Disable the ClusterImageSet and channel subscriptions for disconnected environments.

The configuration of the ACM hub can be customized by using the following variables:


Variable Default Required Description
hub_availability High No Multicluster hub High Availability configuration
hub_disable_selfmanagement False No Do not import the hub cluster as managed in ACM
hub_namespace open-cluster-management No Namespace where ACM has been installed and will be configured
hub_instance multiclusterhub No Name of the multiclusterhub instance to be created (fail if already exists)
hub_disconnected false No If true, it will create custom ClusterImageSets and remove the Channel subscriptions


  1. An Openshift Cluster with a subscription for the ACM operator.
  2. On air-gapped environments, the multicluster-engine operator must be available in the mirrored catalog

It is highly recommended to provision a storage class with enough space available for volumes of the Assisted Service Config before starting deploying clusters. See acm-sno for more details.

Usage example

See below an example of how to use the acm-setup role to configure ACM.

- name: "Setup Advanced Cluster Management"
    name: acm-setup
      hub_disable_selfmanagement: true
      hub_availabilityConfig: High
      hub_disconnected: true


  • acm-sno: A role that deploys an SNO instance using ACM.
  • mirror-ocp-release: A role that mirrors an OCP release to a third-party or local registry.
  • dci-openshfit-agent: An agent that allows the deployment of OCP clusters, it is integrated with DCI (Red Hat Distributed CI).
  • dci-openshfit-app-agent: An agent that allows the deployment of workloads and certification testing on top OCP clusters, it is integrated with DCI (Red Hat Distributed CI).