Update the default values in the .yaml file, according to your needs.

Optional: Disable hub self management, if necessary. By default, the hub cluster is automatically imported and managed by itself, like any other cluster. If you do not want the hub cluster to manage itself, then change the setting for disableHubSelfManagement from false to true. If the setting is not included in the .yaml file that defines the custom resource, add it as shown in the example of the previous step. The following example shows the default template to use if you want to disable the hub self-management feature:

apiVersion: operator.open-cluster-management.io/v1
kind: MultiClusterHub
metadata:
  name: multiclusterhub
  namespace: <namespace>
spec:
  disableHubSelfManagement: true

Replace namespace with the name of your project namespace.

Run the following command to create your secret:

oc create secret generic <secret> -n <namespace> --from-file=.dockerconfigjson=<path-to-pull-secret> --type=kubernetes.io/dockerconfigjson

Replace secret with the name of the secret that you want to create. Replace namespace with your project namespace. Replace path-to-pull-secret with the path to your OpenShift Container Platform pull secret that you downloaded.

Create a .yaml file that defines the operator group. Your file should look similar to the following example:

apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: <default>
spec:
  targetNamespaces:
  - <namespace>

Replace default with the name of your operator group. Replace namespace with the name of your project namespace.

Apply the file that you created to define the operator group:

oc apply -f local/<operator-group>.yaml

Replace operator-group with the name of the operator group .yaml file that you created.

Create a .yaml file that defines the subscription. Your file should look similar to the following example:

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: acm-operator-subscription
spec:
  sourceNamespace: openshift-marketplace
  source: redhat-operators
  channel: release-2.1
  installPlanApproval: Automatic
  name: advanced-cluster-management

Apply the subscription:

oc apply -f local/<subscription>.yaml

Replace subscription with the name of the subscription file that you created.

Create a .yaml file that defines the custom resource.

Optional: Disable hub self management, if necessary. By default, the hub cluster is automatically imported and managed by itself, like any other cluster. If you do not want the hub cluster to manage itself, then change the setting for disableHubSelfManagement from false to true. Your default template should look similar to the following example, if you created a pull secret and are enabling the disableHubSelfManagement feature:

apiVersion: operator.open-cluster-management.io/v1
kind: MultiClusterHub
metadata:
  name: multiclusterhub
  namespace: <namespace>
spec:
  imagePullSecret: <secret>
  disableHubSelfManagement: true

Replace namespace with the name of your project namespace.

Replace secret with the name of your pull secret.

Apply the custom resource:

oc apply -f local/<custom-resource>.yaml

Replace custom-resource with the name of your custom resource file.

Important: The local-cluster namespace is used for the imported self-managed hub cluster. You must not have a local-cluster namespace on your cluster prior to installing. After the local-cluster namespace is created for the hub cluster, anyone who has access to the local-cluster namespace is automatically granted cluster administrator access. For security reasons, do not give anyone access to the local-cluster namespace who does not already have cluster-administrator access.

If this step fails with the following error, the resources are still being created and applied:

error: unable to recognize "./mch.yaml": no matches for kind "MultiClusterHub" in version "operator.open-cluster-management.io/v1"

Run the command again in a few minutes when the resources are created.

Add the certificate information after the additionalTrustBundle line. The resulting content should look similar to the following example:

additionalTrustBundle: |
  -----BEGIN CERTIFICATE-----
  certificate_content
  -----END CERTIFICATE-----
sshKey: >-

Delete the MultiClusterObservability custom resource by entering the following command:

oc delete mco observability

When you delete the resource, the pods in the open-cluster-management-observability namespace on Red Hat Advanced Cluster Management hub cluster, and the pods in open-cluster-management-addon-observability namespace on all managed clusters are removed.

Important: Your object storage is not affected after you remove the observability service.

Copy the following script into a file:

#!/bin/bash
ACM_NAMESPACE=<namespace>
oc delete mch --all -n $ACM_NAMESPACE
helm ls --namespace $ACM_NAMESPACE | cut -f 1 | tail -n +2 | xargs -n 1 helm delete --namespace $ACM_NAMESPACE
oc delete apiservice v1beta1.webhook.certmanager.k8s.io v1.admission.cluster.open-cluster-management.io v1.admission.work.open-cluster-management.io
oc delete clusterimageset --all
oc delete configmap -n $ACM_NAMESPACE cert-manager-controller cert-manager-cainjector-leader-election cert-manager-cainjector-leader-election-core
oc delete consolelink acm-console-link
oc delete crd klusterletaddonconfigs.agent.open-cluster-management.io placementbindings.policy.open-cluster-management.io policies.policy.open-cluster-management.io userpreferences.console.open-cluster-management.io searchservices.search.acm.com
oc delete mutatingwebhookconfiguration cert-manager-webhook cert-manager-webhook-v1alpha1
oc delete oauthclient multicloudingress
oc delete rolebinding -n kube-system cert-manager-webhook-webhook-authentication-reader
oc delete scc kui-proxy-scc
oc delete validatingwebhookconfiguration cert-manager-webhook cert-manager-webhook-v1alpha1

Replace namespace in the script with the name of the namespace where Red Hat Advanced Cluster Management was installed. Ensure that you specify the correct namespace, as the namespace is cleaned out and deleted.

Run the script to remove the artifacts from the previous installation.

Tip: If you plan to reinstall a new version and want to keep your other information, you can skip the rest of the steps in this procedure and reinstall.

Select Delete MultiClusterHub.

It might take up to 20 minutes to complete the uninstall process.