Install

To ensure that the OpenShift Container Platform cluster is set up correctly, access the OpenShift Container Platform web console.

Run the kubectl -n openshift-console get route command to access the OpenShift Container Platform web console.

Configure your infrastructure nodes as infrastructure machine sets according to the procedure in Creating infrastructure machine sets in the Red Hat OpenShift Container Platform documentation.

See the following example of the toleration:

tolerations:
  - effect: NoSchedule
    key: node-role.kubernetes.io/infra
    operator: Exists

Add the following nodeSelector entry to the MultclusterHub resource object section:

spec:
  nodeSelector:
    node-role.kubernetes.io/infra: ""

On the Operator subscription page, select the options for your installation:

Note: To upgrade to the next minor release, you must return to the OperatorHub page and select a new channel for the more current release.

If you plan to import Kubernetes clusters that were not created by OpenShift Container Platform or Red Hat Advanced Cluster Management, create a secret that contains your OpenShift Container Platform pull secret to access the entitled content from the distribution registry. Secret requirements for OpenShift Container Platform clusters are automatically resolved by OpenShift Container Platform and Red Hat Advanced Cluster Management, so you do not have to create the secret if you are not importing other types of Kubernetes clusters to be managed.

Important: These secrets are namespace-specific, so be sure to create a secret in the namespace where you installed Red Hat Advanced Cluster Management.

Create the MultiClusterHub 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. 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. Replace namespace with the name of your project namespace:

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

Select Create to initialize the custom resource. It can take up to 10 minutes for the hub cluster to build and start.

After the hub cluster is created, the status for the operator is Running on the Installed Operators page.

Access the console for the hub cluster.

Create a hub cluster namespace where the operator requirements are contained. Run the following command, where namespace is the name for your hub cluster namespace. The value for namespace might be referred to as Project in the OpenShift Container Platform environment:

oc create namespace <namespace>

Switch your project namespace to the one that you created. Replace namespace with the name of the hub cluster namespace that you created in step 1.

oc project <namespace>

If you plan to import Kubernetes clusters that were not created by OpenShift Container Platform or Red Hat Advanced Cluster Management, generate a secret that contains your OpenShift Container Platform pull secret information to access the entitled content from the distribution registry. The secret requirements for OpenShift Container Platform clusters are automatically resolved by OpenShift Container Platform and Red Hat Advanced Cluster Management, so you do not have to create the secret if you are not importing other types of Kubernetes clusters to be managed. Important: These secrets are namespace-specific, so make sure that you are in the namespace that you created in step 1.

Create an operator group. Each namespace can have only one operator group.

Apply the subscription.

oc apply -f <path-to-file><subscription>.yaml

Apply the MultiClusterHub custom resource.

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

Run the following command to get the custom resource. It can take up to 10 minutes for the MultiClusterHub custom resource status to display as Running in the status.phase field after you run the following command:

oc get mch -o=jsonpath='{.items[0].status.phase}'

After the status is Running, view the list of routes to find your route:

oc get routes

Create a mirror registry, if necessary.

If you do not already have a mirror registry, create one by completing the procedure in the Mirroring images for a disconnected installation topic of the Red Hat OpenShift Container Platform documentation.

If you already have a mirror registry, you can configure and use your existing one.

Bare metal only: Provide the certificate information for the disconnected registry in your install-config.yaml file. To access the image in a protected disconnected registry, you must provide the certificate information so Red Hat Advanced Cluster Management can access the registry.

Create a YAML file that contains the ImageContentSourcePolicy with the name rhacm-policy.yaml . Important: If you modify this on a running cluster, it causes a rolling restart of all nodes.

apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
  name: rhacm-repo
spec:
  repositoryDigestMirrors:
  - mirrors:
    - mirror.registry.com:5000/rhacm2
    source: registry.redhat.io/rhacm2

Apply the ImageContentSourcePolicy file by entering the following command:

oc apply -f rhacm-policy.yaml

Enable the disconnected Operator Lifecycle Manager (OLM) Red Hat Operators and Community Operators.

Red Hat Advanced Cluster Management is included in the OLM Red Hat Operator catalog.

Disable and remove the MultiClusterObservability custom resource, if it is running.

Change to your project namespace by entering the following command:

oc project <namespace>

Replace namespace with the name of your project namespace.

Enter the following command to remove the MultiClusterHub custom resource:

oc delete multiclusterhub --all

It might take up to 20 minutes to complete the uninstall process. You can view the progress by entering the following command:

oc get mch -o yaml

Remove any potential remaining artifacts by running the clean-up script.

Enter the following command to remove all of the related components and subscriptions:

oc delete subs --all

Enter the following command to delete the ClusterServiceVersion:

oc delete clusterserviceversion --all

Remove the MultiClusterObservability custom resource, if installed.

Remove the MultiClusterHub custom resource.

Run the clean-up script according to the procedure in Removing a MultiClusterHub instance by using commands.

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.