Day 1: Installing and configuring IBM Cloud Pak for Multicloud Management

The time has come to install IBM Cloud Pak® for Multicloud Management. You familiarized yourself with the process from Day 0, and now you're ready to get going on installing the platform and getting it configured into a working state.

It's time for all of your careful planning, infrastructure arranging, and thoughtful process designing to spring to life. Day 1 installation is unique from Day 0 and Day 2 in that you are truly at a crossroads. Depending on how you decide to install IBM Cloud Pak for Multicloud Management, your journey takes very different turns.

You can perform a simple or advanced installation. Depending on what course you'd like to take on Day 2, a simple installation gets you up and running almost immediately. The tradeoff is that you might spend more time reconfiguring in the future as you discover details that you would like to change. In either case, you must have cluster administrator access to install and configure IBM Cloud Pak for Multicloud Management.

Table 1. Installation approaches
Installation type Description
Simple installation If you choose the simple installation route, you cannot customize the parameters of any service or module that you are installing, including the default services, on Day 1. You use a form to install, and you choose whether you want to install service or module operators. Default services are always installed. You can customize the parameters on Day 2.
Advanced installation If you choose the advanced installation route, you can use a YAML file for installation. Using the YAML file, you can customize the parameters of the services or modules that you are installing, including the default services, on Day 1. You can choose whether you want to install service or module operators. The default services are always installed. You can further customize the parameters on Day 2.

Notes:

Once you decide which path you'd like to take, identify which of the following services and modules that you want to install on Day 1. You can add them in the future, but it means repeating Day 0 and Day 1 for each addition.

Table 2. Optional installed operators
Capability Operator name For more information
Infrastructure management ibm-management-im-install Infrastructure Management
Infrastructure management ibm-management-infra-grc Policies and Profiles Guide
Infrastructure management ibm-management-infra-vm Provisioning Virtual Machines and Instances
Infrastructure management ibm-management-cam-install Managed services
Infrastructure management ibm-management-service-library Creating and managing services
Operations ibm-management-sre-chatops ChatOps
Monitoring ibm-management-monitoring Monitoring
Security services ibm-management-notary Using a notary service for image signing
Security services ibm-management-image-security-enforcement Image signing support for image policies
Security services ibm-management-mutation-advisor Mutation Advisor Advanced (MA++)
Security services ibm-management-vulnerability-advisor Vulnerability Advisor
Technology preview ibm-management-manage-runtime Managing runtimes

The following services are installed by default when you install the IBM Cloud Pak for Multicloud Management:

Table 3. Default installed operators
Operator name For more information
ibm-management-hybridapp See Application management
ibm-management-hybridgrc-car See IBM Cloud Pak for Multicloud Management Governance and risk
ibm-management-kong See Enabling Kong as API Gateway for IBM Cloud Pak® for Multicloud Management
ibm-management-license-advisor See License Advisor
ibm-management-license-advisor-sender See License Advisor
ibm-management-mcm See Cluster management
ibm-management-secure-tunnel See Using Secure Tunnel to access resources in a private network
ibm-management-sre-bastion See Bastion-based privileged access management system
ibm-management-sre-inventory See Global search
ibm-management-ui See Accessing and using your cluster console
ibm-management-vmpolicy-ansible See IBM Cloud Pak for Multicloud Management Governance and risk