Option 1. Deploying Infrastructure management as a containerized deployment (podified).

Complete these steps to install Infrastructure management as a containerized deployment.


Deploy the ibm-management-im-install operand

Install an instance of the Infrastructure management using the OpenShift Container Platform console or the CLI (command-line tools).

  1. Create an installation instance CR file <im-install-cr.yaml> using the following yaml file and update the applicationDomain, imagePullSecret, initialAdminGroupName and accept license.

    apiVersion: infra.management.ibm.com/v1alpha1
    kind: IMInstall
        app.kubernetes.io/instance: ibm-infra-management-install-operator
        app.kubernetes.io/managed-by: ibm-infra-management-install-operator
        app.kubernetes.io/name: ibm-infra-management-install-operator
      name: im-iminstall
      namespace: management-infrastructure-management
      applicationDomain: <YOUR_IM_HTTPD_ROUTE>
      imagePullPolicy: Always
      imagePullSecret: ibm-management-pull-secret
      initialAdminGroupName: <YOUR_LDAP_USER_GROUP>
        accept: true


    YOUR_IM_HTTPD_ROUTE is a user-defined route, which must include a name for your installation plus part of your IBM Cloud Pak for Multicloud Management console's route. Use the following oc command to obtain the console route and modify it to derive your Infrastructure management route.

    oc -n ibm-common-services get route cp-console --template '{{.spec.host}}'

    Example output:


    Replace the first section cp-console with inframgmtinstall to create YOUR_IM_HTTPD_ROUTE

    For example: inframgmtinstall.apps.mycluster.os.fyre.ibm.com

    YOUR_LDAP_USER_GROUP is an existing user-group defined in your LDAP repository being used by IBM Cloud Pak for Multicloud Management installation. As part of the initial setup, this LDAP group is created in Infrastructure management to match your existing LDAP group by name, and assigned an account role which facilitates SSO login.


    You must specify an LDAP user-group and it must contain at least one user that is able to login to the IBM Cloud Pak for Multicloud Management UI. For example, you have an existing LDAP group that is named group100 and a user with the username user100 is a member of the group. You enter group100 for the value of <YOUR_LDAP_USER_GROUP>.

    databaseRegion Define it only if deploying as part of a multi-region setup. Add the databaseRegion attribute to spec section of the yaml and specify a unique number for the value. If not specified, this value will default to 0. For example, databaseRegion: 99.

    httpdAuthConfig imconnectionsecret

    ACCEPT LICENSE set the accept value to true to accept the license.

  2. Deploy the installation instance CR yaml using one of the following methods:

    • Using the CLI login to your OpenShift cluster where the IBM Cloud Pak for Multicloud Management is installed. For example,

       oc login --token=`<sha256~EUe-BThLn-qRm32K16QDqLMCQZz5VKlM42JKIj2-U7M>` --server=https://`<api.mycluster.os.fyre.ibm.com>`:6443
       oc apply -f im-install-cr.yaml
    • Using the OpenShift Console

      Create an instance to deploy Infrastructure management.

      1. Browse to Operators > Installed Operators.

      2. Switch the project to management-infrastructure-management.

      3. Click IBM Infrastructure Management Install.

      4. Click Create Instance.

      5. Switch to YAML view, select Update YAML.

      6. Copy and paste the installation instance yaml created in step 1.

      7. Click Create.

  3. Verify the pods are running (it can take 15 minutes or more for the pods to start).

    oc get pods -n management-infrastructure-management