Deploying foundational services instance by using the OpenShift console

Complete the following steps to use the form to create the OperandRequest instance. The Create OperandRequest page uses the Form View by default.

1. Provide the following parameters on the form:

   • Name: A name for your OperandRequest instance.
   • Requests: Expand the Requests drawer to specify the list of foundational services that you want to install in your cluster.
     • Operands - Expand the Operands drawer. In the name field, specify the operator name of the service that you want to install in your cluster. For the foundational services operator names, see Foundational services operators and versions. Click Add operand to add as many service operators as you need.
     • registry - Name of the OperandRegistry. Use common-service.
     • description - (Optional) Provide a description of your request.
     • registryNamespace - (Optional) Namespace of OperandRegistry and OperandConfig.
       • If you do not specify a namespace, ODLM looks for OperandRegistry and OperandConfig in the same namespace where you create the OperandRequest, that is, foundational-services.
       • If you specify a namespace, ODLM looks for OperandRegistry and OperandConfig in the namespace that you specified.

2. Click Create.

To view the list of services that are installed in your cluster, go to Operators > Installed Operators.

Complete the following steps to use the YAML to create the OperandRequest instance.

1. On the Create OperandRequest page, select YAML View.

2. Paste the following content in the YAML editor:

   apiVersion: operator.ibm.com/v1alpha1
   kind: OperandRequest
   metadata:
     name: <custom-name-of-operand-request>
     namespace: <your-foundational-services-namespace>
     labels:
       app.kubernetes.io/instance: operand-deployment-lifecycle-manager
       app.kubernetes.io/managed-by: operand-deployment-lifecycle-manager
       app.kubernetes.io/name: operand-deployment-lifecycle-manager
   spec:
     requests:
       - operands:
           - name: ibm-im-operator
           - name: ibm-platformui-operator
         registry: common-service
   

   Note: You can create the OperandRequest in any namespace. If you create the OperandRequest in a different namespace than where OperandRegistry and OperandConfig custom resources are, change the namespace: parameter value to the namespace from where you are creating the OperandRequest. Add the registryNamespace: <your-foundational-services-namespace> parameter in the OperandRequest. See the following example:

   apiVersion: operator.ibm.com/v1alpha1
   kind: OperandRequest
   metadata:
     name: <custom-name-of-operand-request>
     namespace: <OperandRequest namespace>
   spec:
     requests:
       - operands:
           - name: ibm-im-operator
            .
            .
            .
         registry: common-service
         registryNamespace: <your-foundational-services-namespace>
   

3. In the spec.requests.operands section, retain the operator names of the services that you want to install in your cluster. You can remove the services that you do not want. If you want to install additional services that are not listed in the example, reach out to your IBM Cloud Paks team for the operator names.

   Note: The OperandRequest instance name must be unique in the namespace. You can create multiple OperandRequest instances in a namespace.

4. (Optional) Add bindings to access a service. This step is optional. For more information, see Accessing the services.

5. Click Create.

To view the list of services that are installed in your cluster, fo to Operators > Installed Operators.

1. From the navigation pane, click Home > Overview. The cluster status is displayed.

2. Click Operators on the status card. The operator statuses are displayed.

3. Click View all. All the operators that are installed in the cluster are displayed.

4. Check the status of the foundational services operators. All operators must be in the Succeeded status.

   Note: If your operator does not show the Succeeded status, see Operator shows Pending status in a namespace.

To verify the installation, check whether all pods in the foundational services namespace are running. By default, the namespace is foundational-services. You can check from the console by clicking Workloads > Pods under <your-foundational-services-namespace> project. You can also check by using the CLI:

oc get pods -n <your-foundational-services-namespace>

Use the following command to verify whether the foundational services are successfully installed:

oc -n <your-foundational-services-namespace> get csv

Get the URL to access the console.

You can get the IBM Cloud Pak console route for accessing the Administration panel by running the following command:

oc get route -n <your-foundational-services-namespace> cp-console -o jsonpath='{.spec.host}' && echo

The response is your https://<cluster_address>. <cluster_address> is the IBM Cloud Pak console route. Following is a sample output:

cp-console.apps.mycluster.mydomain.com

Based on the example output, your console URL would be https://cp-console.apps.mycluster.mydomain.com.

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

oc -n <your-foundational-services-namespace> get secret platform-auth-idp-credentials -o jsonpath='{.data.admin_username}' | base64 -d && echo

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

oc -n <your-foundational-services-namespace> get secret platform-auth-idp-credentials -o jsonpath='{.data.admin_password}' | base64 -d &&echo

Following is a sample output:

EwK9dj9fwPZHyHTyu9TyIgh9klZSzVsA

Based on the example output, you would use EwK9dj9fwPZHyHTyu9TyIgh9klZSzVsA as the password.

You can change the default password at any time. For more information, see Changing the cluster administrator password.