Skip to content

A task to remove Advanced Cluster Management (ACM) from an OpenShift cluster

Advanced Cluster Management Installation Task

This task installs and configures Red Hat Advanced Cluster Management (ACM) on an OpenShift cluster. It handles the complete installation process including namespace creation, operator subscription, and MultiClusterHub deployment.

Requirements

Parameters

  • openshift/acm-channel: ACM operator subscription channel
  • openshift/acm-install-mcm-timeout: Timeout for MCH installation
  • openshift/acm-install-timeout: Timeout for operator installation
  • openshift/acm-namespace: Target namespace for ACM
  • openshift/acm-operator-name: Name of ACM operator subscription

Cluster Access

  • Administrative access to the OpenShift cluster
  • Valid kubeconfig with cluster-admin privileges
  • Required cluster permissions for operator installation
  • Network access to Red Hat operator catalogs

Resource Requirements

  • Minimum 3 worker nodes recommended
  • At least 8GB RAM available per worker
  • Minimum 4 vCPUs per worker node
  • Sufficient cluster storage for ACM components

Usage

Basic Installation

# Apply task to cluster manager node
drpcli machines tasks add <machine-uuid> openshift-cluster-acm-install

# Monitor installation progress
oc get csv -n <acm-namespace>
oc get pods -n <acm-namespace>

Installation Process

  1. Creates namespace if not exists
  2. Applies OperatorGroup configuration
  3. Creates operator subscription
  4. Waits for operator installation (customizable timeout)
  5. Deploys MultiClusterHub instance
  6. Waits for MCH to be ready (customizable timeout)

Verification

# Check ACM operator status
oc get csv -n open-cluster-management

# Verify MultiClusterHub deployment
oc get multiclusterhub -n open-cluster-management

# Check component pods
oc get pods -n open-cluster-management

Common Issues

  • Timeout during operator installation: Increase openshift/acm-install-timeout
  • MCH deployment failure: Check worker node resources
  • Certificate issues: Verify cluster DNS configuration
  • Pod scheduling failures: Check node taints and tolerations