Quick installation from Red Hat Marketplace

Follow these steps for installing the IBM Cloud Pak® for Multicloud Management from the Red Hat Marketplace.

Note that the following links point to sections within this topic.

Prepare to install the IBM Cloud Pak for Multicloud Management
Install the IBM Cloud Pak for Multicloud Management operator from Red Hat Marketplace
Create the installation instance of IBM Cloud Pak for Multicloud Management
Verify the installation
Access the console
Configure common services IAM as the OAuth identity provider
Enable advanced operators

System requirements

Before you install IBM Cloud Pak, review the required hardware and system configuration settings. For a complete set of requirements, see System requirements.

1. Prepare to install the IBM Cloud Pak for Multicloud Management

1.1 Create an account with Red Hat Marketplace

For more information, check how to create a Red Hat Marketplace account in Red Hat Marketplace Docs Opens in a new tab .

1.2. Prepare the Red Hat OpenShift cluster for the deployment

Provision an Red Hat OpenShift cluster. For more information about the supported versions of Red Hat OpenShift, see Supported OpenShift versions and platforms. The cluster must consist of at least three worker nodes.

Hardware requirements

For more information, see Minimum hardware requirements and recommendations.

Storage

You must have at least one storage class available on the cluster. The advanced operands require a storage class that uses the ReadWriteMany (RWX) mode. It is recommended to install the RWX storage class, such as General Purpose SSD (gp2), Rook Ceph, or ibmc-file-gold, prior to the IBM Cloud Pak installation.

1.3. Register your cluster with Red Hat Marketplace

For more information, check how to register OpenShift cluster with Red Hat Marketplace in Red Hat Marketplace Docs Opens in a new tab .

1.4. Create the project namespace

Create the project namespace for installing IBM Cloud Pak with the following command:

oc create namespace <namespace>

1.5. Import the Red Hat Marketplace pull secret into the namespace

Copy the redhat-marketplace-pull-secret that exists in the openshift-redhat-marketplace namespace into your installation namespace with the following command:

oc get secret redhat-marketplace-pull-secret -n openshift-redhat-marketplace -o yaml | sed 's|openshift-redhat-marketplace|<namespace>|g' | oc apply -f - -n <namespace>

Where <namespace> is the namespace where you install IBM Cloud Pak

1.6. Create an instance of the `ImageContentSourcePolicy` Custom Resource

Create an instance of the ImageContentSourcePolicy Custom Resource with the following contents:

  apiVersion: operator.openshift.io/v1alpha1
  kind: ImageContentSourcePolicy
  metadata:
   name: mirror-config
  spec:
    repositoryDigestMirrors:
      - mirrors:
          - cp.stg.icr.io
        source: cp.icr.io
      - mirrors:
          - cp.stg.icr.io
        source: docker.io/ibmcom
      - mirrors:
          - cp.stg.icr.io
        source: registry.marketplace.redhat.com

1.7. Install the Red Hat® Advanced Cluster Management for Kubernetes operator

See the following Red Hat Advanced Cluster Management documentation for installation instructions:

If your cluster is online, see Installing Red Hat® Advanced Cluster Management for Kubernetes .
If your cluster is offline, see Install on disconnected networks .

1.8. Create the `MultiClusterHub` Custom Resource instance for Red Hat® Advanced Cluster Management for Kubernetes

For more information about how to create the MultiClusterHub Custom Resource instance, see Installing Red Hat Advanced Cluster Management Opens in a new tab in the Red Hat Advanced Cluster Management documentation.

1.9. Create the `MultiClusterObservability` Custom Resource instance for Red Hat® Advanced Cluster Management for Kubernetes

For more information about how to create the MultiClusterObservability Custom Resource instance, see Enabling the observability service in Red Hat Advanced Cluster Management.

2. Install the IBM Cloud Pak for Multicloud Management operator from Red Hat Marketplace

Before you begin the installation, complete the commerce process for Free Trial or Purchase of IBM Cloud Pak for Multicloud Management in Red Hat Marketplace.

Log in to Red Hat Marketplace .
Go to Workspace > Software.
Search for IBM Cloud Pak for Multicloud Management and select the corresponding tile.
Navigate to the Operators tab and click Install Operator.
To install the operator, perform the following actions.
1. Set the update channel to: 2.3-stable.
2. Choose the Automatic approval strategy.
3. Under the Target cluster, select the cluster that you provisioned when preparing to install IBM Cloud Pak. Set the namespace scope to All namespaces.
4. Click Install.
When you are automatically redirected to the Operator detail page, go to the Operator tab. Wait until the Operator status changes to Up to date.
To log in to the OpenShift Container Platform console of the cluster, expand the action menu next to the cluster details and click Cluster Console.

Update the Common Services SecretShare Custom Resource with the following command:

bash <(curl -s https://raw.githubusercontent.com/IBM/cp4mcm-samples/master/scripts/cp4mcm-rhacm21-cp-issuer-secret.sh)

3. Create the installation instance of IBM Cloud Pak for Multicloud Management

Complete these steps from your OpenShift cluster console.

From your OpenShift Container Platform console, switch to your IBM Cloud Pak for Multicloud Management namespace. For example, cp4mcm.
Click Operators > Installed Operators.
Click IBM Cloud Pak for Multicloud Management.
Select Installation tab.
Click Create Installation. The default Form View is displayed.
Provide the following information on the form:
- Name: Specify a name for your installation instance. For example, cp4mcm-install.
- License: Expand the License drawer. Toggle the License Acceptance switch to True to accept the license.
- Image Pull Secret: Select the redhat-marketplace-pull-secret secret that you imported in the 5. Import the Red Hat Marketplace pull secret section.
- Multicloud Management Core Disabled: The default value is True.
- Storage Class: Select the storage class that you want to use. If you do not select any storage class, the default storage class that you set during preparation is used.
Click Create. An installation instance is created with the name that you specified. For example, cp4mcm-install.

You can see the installed default services on the Operator Hub > Installed Operators page in the kube-system namespace.

4. Verify the installation

Check whether the installation succeeded by verifying the pods in those namespaces by using one of the following different methods:

Verify the pod status in the following namespaces:
- Your IBM Cloud Pak for Multicloud Management namespace. For example, cp4mcm.
- ibm-common-services
- kube-system
Verify the pod status in the namespace of any module or service that you enabled.
- management-infrastructure-management
- management-operations
- management-security-services
- management-monitoring
Verify the pod status from the OpenShift Container Platform console.
1. Click Workloads > Pods.
2. Switch to a namespace by selecting it in the Project drop-down list.
3. Verify whether all the pods are running.
Verify pod status from the boot node.
1. Log in to your boot node.
2. Run the oc login command and provide your kubeadmin credentials.
3. Verify the pod status.
```
oc get pods -n <namespace>
```

5. Access the console

Use the following command to get the URL to access the console:

oc get route -n ibm-common-services cp-console -o jsonpath=‘{.spec.host}’

Following is a sample output:

‘cp-console.apps.test-q2.os.example.com’

Based on the example output, your console URL would be https://cp-console.apps.test-q2.os.example.com.

Note: If you access Monitoring menus from the console and a 401 self-signed error message is returned, refer to 401 self-signed certificate error returned when accessing Monitoring menus to troubleshoot.

5.1 Console username and password

Note: This information is for the Default authentication type.

The default username to access the console is admin. You can check the default username by running the following command:

oc -n ibm-common-services get secret platform-auth-idp-credentials -o jsonpath='{.data.admin_username}' | base64 -d && echo

You can get the password for the admin username by running the following command:

oc -n ibm-common-services get secret platform-auth-idp-credentials -o jsonpath='{.data.admin_password}' | base64 -d