1.5. Installing while connected online


Red Hat Advanced Cluster Management for Kubernetes is installed using an operator that deploys all of the required components.

1.5.1. Prerequisites

You must meet the following requirements before you install Red Hat Advanced Cluster Management:

  • Your Red Hat OpenShift Container Platform must have access to the Red Hat Advanced Cluster Management operator in the OperatorHub catalog.
  • OpenShift Container Platform version 4.3, or later, must be deployed in your environment, and you must be logged into it with the CLI. See the OpenShift version 4.3 documentation or OpenShift version 4.4 documentation.
  • Your OpenShift Container Platform command line interface (CLI) must be version 4.3, or later, and configured to run oc commands. See Getting started with the CLI for information about installing and configuring the OpenShift Container Platform CLI.
  • Your Red Hat OpenShift Container Platform permissions must allow you to create a namespace.
  • You must have an Internet connection to access the dependencies for the operator.
  1. Create a hub cluster namespace where the operator requirements are contained:

    oc create namespace <namespace>
    Copy to Clipboard Toggle word wrap

    Replace namespace with a name for your hub cluster namespace. Note: The value for namespace might be referred to as Project in the OpenShift Container Platform environment.

    Important: The Red Hat Advanced Cluster Management operator must be installed in its own namespace. A ServiceAccount with a ClusterRoleBinding automatically gives cluster administrator privileges to Red Hat Advanced Cluster Management and to any ID with access to the namespace. For security, make sure that anyone who is given access to this namespace already has cluster-administrator access.

  2. Switch your project namespace to the one that you created:

    oc project <namespace>
    Copy to Clipboard Toggle word wrap

    Replace namespace with the name of the hub cluster namespace that you created in step 1.

  3. 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.

    1. Download your OpenShift Container Platform pull secret file from cloud.redhat.com/openshift/install/pull-secret by selecting Download pull secret. Your OpenShift Container Platform pull secret is associated with your Red Hat Customer Portal ID, and is the same across all Kubernetes providers.
    2. 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
      Copy to Clipboard Toggle word wrap

      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.

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

    1. 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>
      Copy to Clipboard Toggle word wrap

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

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

      oc apply -f local/<operator-group>.yaml
      Copy to Clipboard Toggle word wrap

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

  5. Apply the subscription.

    1. 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.0
        installPlanApproval: Automatic
        name: advanced-cluster-management
      Copy to Clipboard Toggle word wrap
    2. Apply the subscription:

      oc apply -f local/<subscription>.yaml
      Copy to Clipboard Toggle word wrap

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

  6. Create the MultiClusterHub custom resource by creating a .yaml file that defines the custom resource. Your file should look similar to the following example:

    apiVersion: operator.open-cluster-management.io/v1
    kind: MultiClusterHub
    metadata:
      name: multiclusterhub
      namespace: <namespace>
    spec:
      imagePullSecret: <secret>
    Copy to Clipboard Toggle word wrap

    Replace namespace with your project namespace. Replace secret with the name of the secret that you created.

    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"
    Copy to Clipboard Toggle word wrap

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

  7. View the list of routes after about 10 minutes to find your route:

    oc get routes
    Copy to Clipboard Toggle word wrap

If you are reinstalling Red Hat Advanced Cluster Management and the pods do not start, see Troubleshooting reinstallation failure for steps to work around this problem.

  1. Create a hub cluster namespace for the operator requirements:

    1. In the OpenShift Container Platform console navigation, select Administration > Namespaces.
    2. Select Create Namespace.
    3. Provide a name for your namespace. This is the namespace that you use throughout the installation process. Note: The value for namespace might be referred to as Project in the OpenShift Container Platform environment.
    4. Select Create.

      Important: The Red Hat Advanced Cluster Management operator must be installed in its own namespace. A ServiceAccount with a ClusterRoleBinding automatically gives cluster administrator privileges to Red Hat Advanced Cluster Management and to any ID with access to the namespace. For security, make sure that anyone who is given access to this namespace already has cluster-administrator access.

  2. Switch your project namespace to the one that you created in step 1. This ensures that the steps are completed in the correct namespace. Some resources are namespace-specific.

    1. In the OpenShift Container Platform console navigation, select Administration > Namespaces.
    2. Select the namespace that you created in step 1 from the list.
  3. If you plan to import Kubernetes clusters that were not created by OpenShift Container Platform or Red Hat Advanced Cluster Management, creater 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.

    1. Copy your OpenShift Container Platform pull secret from cloud.redhat.com/openshift/install/pull-secret by selecting Copy pull secret. You will use the content of this pull secret in a step later in this procedure. Your OpenShift Container Platform pull secret is associated with your Red Hat Customer Portal ID, and is the same across all Kubernetes providers.
    2. In the OpenShift Container Platform console navigation, select Workloads > Secrets.
    3. Select Create > Image Pull Secret.
    4. Enter a name for your secret.
    5. Select Upload Configuration File as the authentication type.
    6. In the Configuration file field, paste the pull secret that you copied from cloud.redhat.com.
    7. Select Create to create the secret.
  4. Subscribe to the operator. Note: The value for namespace might be referred to as Project in the OpenShift Container Platform environment.

    1. In the OpenShift Container Platform console navigation, select Operators > OperatorHub.
    2. Select Red Hat Advanced Cluster Management. Tip: You can filter on the Integration & Delivery category to narrow the choices.
    3. Select Install.
    4. Update the values, if necessary.
    5. Select Subscribe.
  5. Create the MultiClusterHub custom resource.

    1. In the OpenShift Container Platform console navigation, select Installed Operators > Advanced Cluster Management for Kubernetes.
    2. Select the MultiClusterHub tab.
    3. Select Create MultiClusterHub.
    4. Update the values, according to your needs. Tip: You can edit the values in the YAML file by selecting YAML View. Some of the values are only available in the YAML view. The following example shows some sample data in the YAML view:

      apiVersion: operator.open-cluster-management.io/v1
      kind: MultiClusterHub
      metadata:
        namespace: <namespace>
        name: multiclusterhub
      spec: {}
      Copy to Clipboard Toggle word wrap

      Add the secret that you created to the imagePullSecret field on the console. In the YAML View, confirm that the namespace is your project namespace.

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

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

  7. Access the console for the hub.

    1. In the OpenShift Container Platform console navigation, select Networking > Routes.
    2. View the URL for your hub in the list, and navigate to it to access the console for your hub.

If you are reinstalling Red Hat Advanced Cluster Management and the pods do not start, see Troubleshooting reinstallation failure for steps to work around this problem.

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat