Advanced configuration

The installation YAML file contains the configuration settings that are needed to deploy IBM Cloud Pak® for Multicloud Management in your cluster.

You can update these parameters before you install IBM Cloud Pak for Multicloud Management. Or, you can first install IBM Cloud Pak for Multicloud Management, then use the same installation instance to change the YAML parameter values.

Creating an instance for IBM Cloud Pak for Multicloud Management installation
Editing the IBM Cloud Pak for Multicloud Management installation instance to configure services or modules
Adding the configuration parameters
Configuring available operators

Creating an instance for IBM Cloud Pak for Multicloud Management installation

Complete these steps to create an installation instance and to provide the configuration parameters. By default, all modules and services are disabled. If you want to enable a service or module, set spec.pakModules.config.enabled to true for that module or service.

From your OpenShift Container Platform console, switch to the namespace where you created the IBM Cloud Pak for Multicloud Management operator. For example, cp4mcm.
Click Operators > Installed Operators.
Click IBM Cloud Pak for Multicloud Management.
Select the Installation tab.
Click Create Installation. The Installation YAML file content is displayed in the YAML editor.
Provide the following configurations for installing the IBM Cloud Pak for Multicloud Management core components. You provide the configuration for the services and modules in the next step. Update the following parameters in the spec: section.
```
apiVersion: orchestrator.management.ibm.com/v1alpha1
kind: Installation
metadata:
  name: <name-of-the-installation-instance>
  namespace: <cloud-pak-namespace>
spec:
  storageClass: <storage-class-name-to-be-used-for-the-cloud-pak>
  imagePullSecret: <entitled-registry-secret-name>
  license:
    accept: <`true` or `false`>
  mcmCoreDisabled: true  
  pakModules:
  .
  .
  .
```
- storageClass - Specify the storage class that you want to use. If you do not specify any storage class, the default storage class that you set during preparation is used.
- imagePullSecret - Specify the entitled registry secret that you created during Preparing an online cluster for installation or Preparing an offline cluster for installation.
- license - You must change the value to true; default value is false.
Following is an example of the updated configuration:
```
apiVersion: orchestrator.management.ibm.com/v1alpha1
kind: Installation
metadata:
  name: cp4mcm-install
  namespace: cp4mcm
spec:
  storageClass: rook-ceph-block-internal
  imagePullSecret: my-er-key
  license:
    accept: true
  mcmCoreDisabled: true  
  pakModules:
  .
  .
  .
```
Provide the configuration for the services or modules that you want to install. For more information, see Configuration parameters.
Click Create.

Editing the IBM Cloud Pak for Multicloud Management installation instance to configure services or modules

Complete these steps to configure services or modules after you installed IBM Cloud Pak for Multicloud Management.

From your OpenShift Container Platform console, switch to the namespace where you created the IBM Cloud Pak for Multicloud Management installation instance. For example, cp4mcm.
Click Operators > Installed Operators.
Click IBM Cloud Pak for Multicloud Management.
Select the Installation tab.
Select the installation instance. For example, cp4mcm-install. The Installation YAML file content is displayed in the YAML editor.
Provide the configuration for the services or modules that you want to install. For more information, see Configuration parameters.
Click Save.

Adding the configuration parameters

In the Installation YAML file, add or modify the parameters and values in the spec.pakModules.config.- name.<service or module-name>.spec section.

Set spec.pakModules.config.enabled to true.

Update the parameters in the spec.pakModules.config.- name.<service or module-name>.spec section.

For example, by default, Monitoring is disabled. See the following default configuration:

 apiVersion: orchestrator.management.ibm.com/v1alpha1
 kind: Installation
 metadata:
   name: example-installation
   namespace: cp4mcm
   spec:
     storageClass: ''
     imagePullSecret: my-er-key
     license:
       accept: false
     mcmCoreDisabled: true  
     pakModules:
     .
     .
       - config:
           - enabled: true
             name: ibm-management-monitoring
             spec: {}
         enabled: false
         name: monitoring
     .
     .

To install Monitoring, change enabled: false to enabled: true. Then, update the parameters in the spec section, as required. For example, if you provided a storage class for Monitoring, the updated YAML content would resemble the following code:

 apiVersion: orchestrator.management.ibm.com/v1alpha1
 kind: Installation
 metadata:
   name: cp4mcm-install
   namespace: cp4mcm
   spec:
     storageClass: rook-ceph-block-internal
     imagePullSecret: my-er-key
     license:
       accept: true
     mcmCoreDisabled: true  
     pakModules:
     .
     .
       - config:
           - enabled: true
             name: ibm-management-monitoring
             spec:
               monitoringDeploy:
                 global:
                   persistence:
                     storageClassName: default
         enabled: true
         name: monitoring
     .
     .

Monitoring has more configuration options available, as described in Monitoring configuration. The configuration for each service differs.

Configuring available operators

Following sections provide information about the available operator categories and their configuration parameters.

Default services

Foundation services are installed by default when you install IBM Cloud Pak for Multicloud Management. These services are installed in the kube-system namespace. For more information about configuring these services, see Default services configuration.

Infrastructure management

The Infrastructure management and Managed services are installed in the management-infrastructure-management namespace. For more information about configuring these services, see Infrastructure management configuration.

Operations

Note: Do not install this operator if you are installing on a Linux® on Power® (ppc64le) cluster. ChatOps (ibm-management-sre-chatops) is not supported on a Linux® on Power® (ppc64le) platform.

ChatOps is installed in the management-operations namespace. You must install the ChatOps operator with the default parameters. There are no parameters that you can update.

By default ChatOps is disabled. You need to open the IBM Cloud Pak® for Multicloud Management installation YAML file, locate the Operations module and change enabled: false to enabled: true. For more information, see Adding the configuration parameters.

For how to create the ChatOps operand, see Deploying ChatOps.

For how to use ChatOps, see Using ChatOps.

Monitoring

Monitoring is installed in the management-monitoring namespace. Monitoring has additional parameters that must be customized before installation. For more information, see Monitoring configuration.

Security services

The security services are installed in the management-security-services namespace. For more information about the configuration parameters, see Security configuration.

Technology preview

The Manage Runtime technology preview module is installed in the kube-system namespace. You must install the Manage Runtime operator with the default configuration. There are no parameters that you can update.