Table of contents

Creating operator subscriptions

An operator subscription tells the cluster where to install a given operator and gives information about the operator to Operator Lifecycle Manager (OLM).

When you create an operator subscription, OLM gets the cluster service version (CSV) for the operator. The CSV describes the operator, and OLM uses the CSV to:
  • Introduce the custom resource definition (CRD) if it doesn't exist
  • Set up the operator's service accounts
  • Start up the operator deployment

Procedure

Complete the following tasks to create the relevant operator subscriptions on your cluster:

1. Choosing an install plan

When you create an operator subscription, you specify the install plan for the operator; you can specify whether you want to manually or automatically upgrade the operator.

Automatic
If you specify installPlanApproval: Automatic, Red Hat® OpenShift® Container Platform will automatically load newer versions of the operator if they are available. For example, if you mirror images to a private container registry and you set the install plan to automatic, Red Hat OpenShift Container Platform will automatically use the latest version of the operator that is available in the private container registry.
Manual
If you specify installPlanApproval: Manual, OLM creates an update request when a newer version of an operator is available. A cluster administrator must manually approve the update request to update the operator to the newer version.
Best practice: It is recommended that you use the automatic install plan.

Upgrading the operator does not impact the version of the software that is running on the cluster. It updates only the operator.

An operator manages the software.

For an in-depth description of operators, see the Red Hat OpenShift: Operators Framework video from Red Hat.

All of the operator subscriptions in this topic specify the automatic install plan (installPlanApproval: Automatic).

2. Creating an operator subscription for the scheduling service

If you don't plan to install the scheduling service, you can skip this step.

Create the appropriate operator subscription for your environment:

Image location Required subscriptions
IBM® Entitled Registry If you are pulling images from the publicly available registry:
  1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
    cat <<EOF |oc apply -f -
    apiVersion: operators.coreos.com/v1alpha1
    kind: Subscription
    metadata:
      name: ibm-cpd-scheduling-catalog-subscription
      namespace: ibm-common-services    # Specify the project that contains the Cloud Pak foundational services operators
    spec:
      channel: v1.2
      installPlanApproval: Automatic
      name: ibm-cpd-scheduling-operator
      source: ibm-operator-catalog
      sourceNamespace: openshift-marketplace
    EOF
  2. Validate that the operator was successfully created.
    1. Run the following command to confirm that the subscription was triggered:
      oc get sub -n ibm-common-services ibm-cpd-scheduling-catalog-subscription \
      -o jsonpath='{.status.installedCSV} {"\n"}'

      Verify that the command returns ibm-cpd-scheduling-operator.v1.2.2.

    2. Run the following command to confirm that the cluster service version (CSV) is ready:
      oc get csv -n ibm-common-services ibm-cpd-scheduling-operator.v1.2.2 \
      -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

      Verify that the command returns Succeeded : install strategy completed with no errors.

    3. Run the following command to confirm that the operator is ready:
      oc get deployments -n ibm-common-services -l olm.owner="ibm-cpd-scheduling-operator.v1.2.2" \
      -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

      Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

Private container registry If you are pulling images from a private container registry,
  1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
    cat <<EOF |oc apply -f -
    apiVersion: operators.coreos.com/v1alpha1
    kind: Subscription
    metadata:
      name: ibm-cpd-scheduling-catalog-subscription
      namespace: ibm-common-services    # Specify the project that contains the Cloud Pak foundational services operators
    spec:
      channel: v1.2
      installPlanApproval: Automatic
      name: ibm-cpd-scheduling-operator
      source: ibm-cpd-scheduling-catalog
      sourceNamespace: openshift-marketplace
    EOF
  2. Validate that the operator was successfully created.
    1. Run the following command to confirm that the subscription was triggered:
      oc get sub -n ibm-common-services ibm-cpd-scheduling-catalog-subscription \
      -o jsonpath='{.status.installedCSV} {"\n"}'

      Verify that the command returns ibm-cpd-scheduling-operator.v1.2.2.

    2. Run the following command to confirm that the cluster service version (CSV) is ready:
      oc get csv -n ibm-common-services ibm-cpd-scheduling-operator.v1.2.2 \
      -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

      Verify that the command returns Succeeded : install strategy completed with no errors.

    3. Run the following command to confirm that the operator is ready:
      oc get deployments -n ibm-common-services -l olm.owner="ibm-cpd-scheduling-operator.v1.2.2" \
      -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

      Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

3. Creating an operator subscription for the IBM Cloud Pak for Data platform operator

Create the appropriate operator subscription for your environment:

Image location Required subscriptions
IBM Entitled Registry If you are pulling images from the publicly available registry:
  1. Create the Cloud Pak for Data operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
    cat <<EOF |oc apply -f -
    apiVersion: operators.coreos.com/v1alpha1
    kind: Subscription
    metadata:
      name: cpd-operator
      namespace: ibm-common-services|cpd-operators    # Pick the project where you want to install the Cloud Pak for Data platform operator
    spec:
      channel: v2.0
      installPlanApproval: Automatic
      name: cpd-platform-operator
      source: ibm-operator-catalog
      sourceNamespace: openshift-marketplace
    EOF
  2. If you are running a specialized installation (installing the IBM Cloud Pak® for Data platform operator and the IBM Cloud Pak foundational services in separate projects), create an operator subscription for the IBM NamespaceScope Operator in the IBM Cloud Pak for Data platform operator project:
    cat <<EOF |oc apply -f -
    apiVersion: operators.coreos.com/v1alpha1
    kind: Subscription
    metadata:
      name: ibm-namespace-scope-operator
      namespace: cpd-operators
    spec:
      channel: v3
      installPlanApproval: Automatic
      name: ibm-namespace-scope-operator
      source: ibm-operator-catalog
      sourceNamespace: openshift-marketplace
    EOF
  3. Validate that the operator was successfully created.

    For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

    1. Run the following command to confirm that the subscription was triggered:
      oc get sub -n operator-project cpd-operator \
      -o jsonpath='{.status.installedCSV} {"\n"}'

      Verify that the command returns cpd-platform-operator.v2.0.3.

    2. Run the following command to confirm that the cluster service version (CSV) is ready:
      oc get csv -n operator-project cpd-platform-operator.v2.0.3 \
      -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

      Verify that the command returns Succeeded : install strategy completed with no errors.

    3. Run the following command to confirm that the operator is ready:
      oc get deployments -n operator-project -l olm.owner="cpd-platform-operator.v2.0.3" \
      -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

      Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

Private container registry If you are pulling images from a private container registry:
  1. Create the Cloud Pak for Data operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
    cat <<EOF |oc apply -f -
    apiVersion: operators.coreos.com/v1alpha1
    kind: Subscription
    metadata:
      name: cpd-operator
      namespace: ibm-common-services|cpd-operators    #  Pick the project where you want to install the Cloud Pak for Data platform operator
    spec:
      channel: v2.0
      installPlanApproval: Automatic
      name: cpd-platform-operator
      source: cpd-platform
      sourceNamespace: openshift-marketplace
    EOF
  2. If you are running a specialized installation (installing the IBM Cloud Pak for Data platform operator and the IBM Cloud Pak foundational services in separate projects), create an operator subscription for the IBM NamespaceScope Operator in the IBM Cloud Pak for Data platform operator project:
    cat <<EOF |oc apply -f -
    apiVersion: operators.coreos.com/v1alpha1
    kind: Subscription
    metadata:
      name: ibm-namespace-scope-operator
      namespace: cpd-operators
    spec:
      channel: v3
      installPlanApproval: Automatic
      name: ibm-namespace-scope-operator
      source: opencloud-operators
      sourceNamespace: openshift-marketplace
    EOF
  3. Validate that the operator was successfully created.

    For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

    1. Run the following command to confirm that the subscription was triggered:
      oc get sub -n operator-project cpd-operator \
      -o jsonpath='{.status.installedCSV} {"\n"}'

      Verify that the command returns cpd-platform-operator.v2.0.3.

    2. Run the following command to confirm that the cluster service version (CSV) is ready:
      oc get csv -n operator-project cpd-platform-operator.v2.0.3 \
      -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

      Verify that the command returns Succeeded : install strategy completed with no errors.

    3. Run the following command to confirm that the operator is ready:
      oc get deployments -n operator-project -l olm.owner="cpd-platform-operator.v2.0.3" \
      -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

      Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

4. Enabling services to use namespace scoping with third-party operators

Some services have dependencies on third-party operators, such as open source operators. By default, the service has no control over the namespace scope of these third-party operators.

However, you can enable the csvInjector option in the IBM NamespaceScope Operator to ensure that the required third-party operators use the same namespace scope as the service that requires them. (Setting the csvInjector option enables a service to augment the cluster service version (CSV) of a third-party operator.)

To ensure that the service can update the CSV, you must enable the csvInjector option before you create the operator subscription for the service.

This setting is required for the following services:
  • Data Virtualization
  • Db2® Data Management Console
  • IBM Match 360 with Watson™
  • Watson Assistant
  • Watson Assistant for Voice Interaction
  • Watson Discovery
  • Watson Speech to Text
  • Watson Text to Speech

To update the IBM NamespaceScope Operator, run the appropriate command for your environment:

  • Run the following command to update the IBM NamespaceScope Operator in the ibm-common-services project:
    oc patch NamespaceScope common-service \
    -n ibm-common-services \
    --type=merge \
    --patch='{"spec": {"csvInjector": {"enable": true} } }'
  • Run the following command to update the IBM NamespaceScope Operator in the cpd-operators project:

    cat <<EOF |oc apply -f -
    apiVersion: operator.ibm.com/v1
    kind: NamespaceScope
    metadata:
      name: cpd-operators
      namespace: cpd-operators        # (Default) Replace with the Cloud Pak for Data platform operator project name
    spec:
      csvInjector:
        enable: true
      namespaceMembers:
      - cpd-operators                 # (Default) Replace with the Cloud Pak for Data platform operator project name
    EOF

5. Creating an operator subscription for services

Create the operator subscription for each service that you plan to install.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-ae-operator-subscription
          app.kubernetes.io/managed-by: ibm-cpd-ae-operator
          app.kubernetes.io/name: ibm-cpd-ae-operator-subscription
        name: ibm-cpd-ae-operator-subscription
        namespace: ibm-common-services|cpd-operators     # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: stable-v1
          installPlanApproval: Automatic
          name: analyticsengine-operator
          source: ibm-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-ae-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-ae.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-ae.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-ae.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-ae-operator-subscription
          app.kubernetes.io/managed-by: ibm-cpd-ae-operator
          app.kubernetes.io/name: ibm-cpd-ae-operator-subscription
        name: ibm-cpd-ae-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: stable-v1
          installPlanApproval: Automatic
          name: analyticsengine-operator
          source: ibm-cpd-ae-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-ae-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-ae.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-ae.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-ae.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-ca-operator-catalog-subscription
        labels:
          app.kubernetes.io/instance: ibm-ca-operator
          app.kubernetes.io/managed-by: ibm-ca-operator
          app.kubernetes.io/name: ibm-ca-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v4.0
        name: ibm-ca-operator
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-ca-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-ca-operator.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-ca-operator.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-ca-operator.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-ca-operator-catalog-subscription
        labels:
          app.kubernetes.io/instance: ibm-ca-operator
          app.kubernetes.io/managed-by: ibm-ca-operator
          app.kubernetes.io/name: ibm-ca-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v4.0
        name: ibm-ca-operator
        installPlanApproval: Automatic
        source: ibm-ca-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-ca-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-ca-operator.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-ca-operator.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-ca-operator.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cde-operator-subscription
          app.kubernetes.io/managed-by: ibm-cde-operator
          app.kubernetes.io/name: ibm-cde-operator-subscription
        name: ibm-cde-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        installPlanApproval: Automatic
        name: ibm-cde-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cde-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-cde.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-cde.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-cde.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cde-operator-subscription
          app.kubernetes.io/managed-by: ibm-cde-operator
          app.kubernetes.io/name: ibm-cde-operator-subscription
        name: ibm-cde-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        installPlanApproval: Automatic
        name: ibm-cde-operator
        source: ibm-cde-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cde-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-cde.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-cde.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-cde.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • The operator subscription for Data Refinery is automatically created when you create the operator subscription for either Watson Knowledge Catalog or Watson Studio.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the Db2U operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2u-operator
        namespace: ibm-common-services|cpd-operators # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.1
        name: db2u-operator
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2u-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns db2u-operator.v1.1.5.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project db2u-operator.v1.1.5 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="db2u-operator.v1.1.5" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. Create the Data Virtualization operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-dv-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.7
        installPlanApproval: Automatic
        name: ibm-dv-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-dv-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-dv-operator.v1.7.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-dv-operator.v1.7.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-dv-operator.v1.7.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the Db2U operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2u-operator
        namespace: ibm-common-services|cpd-operators # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.1
        name: db2u-operator
        installPlanApproval: Automatic
        source: ibm-db2uoperator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2u-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns db2u-operator.v1.1.5.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project db2u-operator.v1.1.5 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="db2u-operator.v1.1.5" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. Create the Data Virtualization operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-dv-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.7
        installPlanApproval: Automatic
        name: ibm-dv-operator
        source: ibm-dv-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-dv-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-dv-operator.v1.7.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-dv-operator.v1.7.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-dv-operator.v1.7.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • The operator subscription is the same for DataStage Enterprise or DataStage Enterprise Plus.

    Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata: 
        name: ibm-datastage-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec: 
        channel: v1.0
        installPlanApproval: Automatic 
        name: ibm-datastage-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-datastage-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-datastage-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-datastage-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-datastage-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata: 
        name: ibm-datastage-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec: 
        channel: v1.0
        installPlanApproval: Automatic 
        name: ibm-datastage-operator
        source: ibm-datastage-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-datastage-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-datastage-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-datastage-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-datastage-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscriptions for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Specialized installations only. By default, IBM Cloud Pak foundational services expects that the Db2U operator (ibm-db2u-operator) is installed in the ibm-common-services project. However, if you are using the specialized installation architecture (where the IBM Cloud Pak foundational services operators and Cloud Pak for Data operators are in separate OpenShift projects), you must edit the IBM Cloud Pak foundational services operand registry to point to the project where the Cloud Pak for Data operators are installed:
      1. Run the following command to edit the IBM Cloud Pak foundational services operand registry:
        oc edit operandRegistry common-service
      2. Change the value of the namespace entry for the ibm-db2u-operator. Specify the OpenShift project where the Cloud Pak for Data operators are installed, for example, cpd-operators:
         - channel: v1.1
            installPlanApproval: Automatic
            name: ibm-db2u-operator
            namespace: cpd-operators    # Specify the project where the Cloud Pak for Data operators are installed
            packageName: db2u-operator
            scope: public
            sourceName: ibm-db2uoperator-catalog
            sourceNamespace: openshift-marketplace
      3. Save your changes and exit. For example, if you are using vi, hit esc and enter :wq.
    2. Create the Db2 operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2oltp-cp4d-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-db2oltp-cp4d-operator
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    3. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2oltp-cp4d-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-db2oltp-cp4d-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-db2oltp-cp4d-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-db2oltp-cp4d-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Specialized installations only. By default, IBM Cloud Pak foundational services expects that the Db2U operator (ibm-db2u-operator) is installed in the ibm-common-services project. However, if you are using the specialized installation architecture (where the IBM Cloud Pak foundational services operators and Cloud Pak for Data operators are in separate OpenShift projects), you must edit the IBM Cloud Pak foundational services operand registry to point to the project where the Cloud Pak for Data operators are installed:
      1. Run the following command to edit the IBM Cloud Pak foundational services operand registry:
        oc edit operandRegistry common-service
      2. Change the value of the namespace entry for the ibm-db2u-operator. Specify the OpenShift project where the Cloud Pak for Data operators are installed, for example, cpd-operators:
         - channel: v1.1
            installPlanApproval: Automatic
            name: ibm-db2u-operator
            namespace: cpd-operators    # Specify the project where the Cloud Pak for Data operators are installed
            packageName: db2u-operator
            scope: public
            sourceName: ibm-db2uoperator-catalog
            sourceNamespace: openshift-marketplace
      3. Save your changes and exit. For example, if you are using vi, hit esc and enter :wq.
    2. Create the Db2 operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2oltp-cp4d-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-db2oltp-cp4d-operator
        installPlanApproval: Automatic
        source: ibm-db2oltp-cp4d-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    3. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2oltp-cp4d-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-db2oltp-cp4d-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-db2oltp-cp4d-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-db2oltp-cp4d-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the Db2U operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2u-operator
        namespace: ibm-common-services|cpd-operators # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.1
        name: db2u-operator
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2u-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns db2u-operator.v1.1.5.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project db2u-operator.v1.1.5 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="db2u-operator.v1.1.5" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. Create the Db2 Big SQL operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-bigsql-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:   
        channel: v7.2
        installPlanApproval: Automatic
        name: ibm-bigsql-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-bigsql-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-bigsql-operator.v7.2.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-bigsql-operator.v7.2.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-bigsql-operator.v7.2.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the Db2U operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2u-operator
        namespace: ibm-common-services|cpd-operators # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.1
        name: db2u-operator
        installPlanApproval: Automatic
        source: ibm-db2uoperator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2u-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns db2u-operator.v1.1.5.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project db2u-operator.v1.1.5 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="db2u-operator.v1.1.5" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. Create the Db2 Big SQL operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-bigsql-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:   
        channel: v7.2
        installPlanApproval: Automatic
        name: ibm-bigsql-operator
        source: ibm-bigsql-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-bigsql-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-bigsql-operator.v7.2.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-bigsql-operator.v7.2.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-bigsql-operator.v7.2.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-datagate-operator-subscription
          app.kubernetes.io/managed-by: ibm-datagate-operator
          app.kubernetes.io/name: ibm-datagate-operator-subscription
        name: ibm-datagate-operator-subscription
        namespace: ibm-common-services|cpd-operators   # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v2.0
          installPlanApproval: Automatic
          name: ibm-datagate-operator
          source: ibm-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-datagate-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-datagate-operator.v2.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-datagate-operator.v2.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-datagate-operator.v2.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-datagate-operator-subscription
          app.kubernetes.io/managed-by: ibm-datagate-operator
          app.kubernetes.io/name: ibm-datagate-operator-subscription
        name: ibm-datagate-operator-subscription
        namespace: ibm-common-services|cpd-operators   # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v2.0
          installPlanApproval: Automatic
          name: ibm-datagate-operator
          source: ibm-datagate-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-datagate-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-datagate-operator.v2.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-datagate-operator.v2.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-datagate-operator.v2.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-dmc-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        installPlanApproval: Automatic
        name: ibm-dmc-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-dmc-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-databases-dmc.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-databases-dmc.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-databases-dmc.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-dmc-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        installPlanApproval: Automatic
        name: ibm-dmc-operator
        source: ibm-dmc-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-dmc-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-databases-dmc.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-databases-dmc.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-databases-dmc.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Not applicable. Contact IBM Software support if you plan to install this service.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Specialized installations only. By default, IBM Cloud Pak foundational services expects that the Db2U operator (ibm-db2u-operator) is installed in the ibm-common-services project. However, if you are using the specialized installation architecture (where the IBM Cloud Pak foundational services operators and Cloud Pak for Data operators are in separate OpenShift projects), you must edit the IBM Cloud Pak foundational services operand registry to point to the project where the Cloud Pak for Data operators are installed:
      1. Run the following command to edit the IBM Cloud Pak foundational services operand registry:
        oc edit operandRegistry common-service
      2. Change the value of the namespace entry for the ibm-db2u-operator. Specify the OpenShift project where the Cloud Pak for Data operators are installed, for example, cpd-operators:
         - channel: v1.1
            installPlanApproval: Automatic
            name: ibm-db2u-operator
            namespace: cpd-operators    # Specify the project where the Cloud Pak for Data operators are installed
            packageName: db2u-operator
            scope: public
            sourceName: ibm-db2uoperator-catalog
            sourceNamespace: openshift-marketplace
      3. Save your changes and exit. For example, if you are using vi, hit esc and enter :wq.
    2. Create the Db2 Warehouse operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2wh-cp4d-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-db2wh-cp4d-operator
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    3. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2wh-cp4d-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-db2wh-cp4d-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-db2wh-cp4d-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-db2wh-cp4d-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Specialized installations only. By default, IBM Cloud Pak foundational services expects that the Db2U operator (ibm-db2u-operator) is installed in the ibm-common-services project. However, if you are using the specialized installation architecture (where the IBM Cloud Pak foundational services operators and Cloud Pak for Data operators are in separate OpenShift projects), you must edit the IBM Cloud Pak foundational services operand registry to point to the project where the Cloud Pak for Data operators are installed:
      1. Run the following command to edit the IBM Cloud Pak foundational services operand registry:
        oc edit operandRegistry common-service
      2. Change the value of the namespace entry for the ibm-db2u-operator. Specify the OpenShift project where the Cloud Pak for Data operators are installed, for example, cpd-operators:
         - channel: v1.1
            installPlanApproval: Automatic
            name: ibm-db2u-operator
            namespace: cpd-operators    # Specify the project where the Cloud Pak for Data operators are installed
            packageName: db2u-operator
            scope: public
            sourceName: ibm-db2uoperator-catalog
            sourceNamespace: openshift-marketplace
      3. Save your changes and exit. For example, if you are using vi, hit esc and enter :wq.
    2. Create the Db2 Warehouse operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2wh-cp4d-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-db2wh-cp4d-operator
        installPlanApproval: Automatic
        source: ibm-db2wh-cp4d-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    3. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2wh-cp4d-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-db2wh-cp4d-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-db2wh-cp4d-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-db2wh-cp4d-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-dods-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-dods-operator
          app.kubernetes.io/name: ibm-cpd-dods-operator-catalog-subscription
        name: ibm-cpd-dods-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v4.0
          installPlanApproval: Automatic
          name: ibm-cpd-dods
          source: ibm-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-dods-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-dods.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-dods.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-dods.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-dods-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-dods-operator
          app.kubernetes.io/name: ibm-cpd-dods-operator-catalog-subscription
        name: ibm-cpd-dods-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v4.0
          installPlanApproval: Automatic
          name: ibm-cpd-dods
          source: ibm-cpd-dods-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-dods-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-dods.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-dods.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-dods.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the PostgreSQL operator subscription.
      Important: This operator is installed in the openshift-operators project. The operator does not support namespace scoping and must be installed as cluster-wide resource.
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: cloud-native-postgresql-catalog-subscription
        namespace: openshift-operators
      spec:
        channel: stable
        name: cloud-native-postgresql
        installPlanApproval: Automatic
        source: cloud-native-postgresql-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.
      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n openshift-operators cloud-native-postgresql-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns cloud-native-postgresql.v1.6.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n openshift-operators cloud-native-postgresql.v1.6.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n openshift-operators -l olm.owner="cloud-native-postgresql.v1.6.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. Create the EDB Postgres operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-cpd-edb-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        installPlanApproval: Automatic
        channel: stable
        name: ibm-cpd-edb
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-edb-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-edb.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-edb.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-edb.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the PostgreSQL operator subscription.
      Important: This operator is installed in the openshift-operators project. The operator does not support namespace scoping and must be installed as cluster-wide resource.
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: cloud-native-postgresql-catalog-subscription
        namespace: openshift-operators
      spec:
        channel: stable
        name: cloud-native-postgresql
        installPlanApproval: Automatic
        source: cloud-native-postgresql-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.
      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n openshift-operators cloud-native-postgresql-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns cloud-native-postgresql.v1.6.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n openshift-operators cloud-native-postgresql.v1.6.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n openshift-operators -l olm.owner="cloud-native-postgresql.v1.6.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. Create the EDB Postgres operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-cpd-edb-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        installPlanApproval: Automatic
        channel: stable
        name: ibm-cpd-edb
        source: ibm-cpd-edb-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-edb-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-edb.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-edb.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-edb.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-hadoop-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-hadoop-operator
          app.kubernetes.io/name: ibm-cpd-hadoop-operator-catalog-subscription
        name: ibm-cpd-hadoop-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.0
          installPlanApproval: Automatic
          name: ibm-cpd-hadoop
          source: ibm-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-hadoop-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-hadoop.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-hadoop.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-hadoop.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-hadoop-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-hadoop-operator
          app.kubernetes.io/name: ibm-cpd-hadoop-operator-catalog-subscription
        name: ibm-cpd-hadoop-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.0
          installPlanApproval: Automatic
          name: ibm-cpd-hadoop
          source: ibm-cpd-hadoop-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-hadoop-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-hadoop.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-hadoop.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-hadoop.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Not applicable. For details, see the Financial Services Workbench documentation.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-mdm-operator-subscription
          app.kubernetes.io/managed-by: ibm-mdm-operator
          app.kubernetes.io/name: ibm-mdm-operator-subscription
        name: ibm-mdm-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.1
        installPlanApproval: Automatic
        name: ibm-mdm
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-mdm-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-mdm.v1.1.14.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-mdm.v1.1.14 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-mdm.v1.1.14" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-mdm-operator-subscription
          app.kubernetes.io/managed-by: ibm-mdm-operator
          app.kubernetes.io/name: ibm-mdm-operator-subscription
        name: ibm-mdm-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.1
        installPlanApproval: Automatic
        name: ibm-mdm
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-mdm-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-mdm.v1.1.14.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-mdm.v1.1.14 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-mdm.v1.1.14" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • See Watson Studio Runtimes.

  • See Watson Studio Runtimes.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the MongoDB Enterprise (third-party) operator subscription.
      Important: This operator is installed in the openshift-operators project. The operator does not support namespace scoping and must be installed as cluster-wide resource.
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-mongodb-enterprise-catalog-subscription
        namespace: openshift-operators
      spec:
        channel: stable
        name: mongodb-enterprise
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.
      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n openshift-operators ibm-mongodb-enterprise-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns mongodb-enterprise.v1.10.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n openshift-operators mongodb-enterprise.v1.10.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n openshift-operators -l olm.owner="mongodb-enterprise.v1.10.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. Create the MongoDB (Cloud Pak for Data) operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-cpd-mongodb-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: stable
        name: ibm-cpd-mongodb
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-mongodb-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-mongodb.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-mongodb.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-mongodb.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the MongoDB Enterprise (third-party) operator subscription.
      Important: This operator is installed in the openshift-operators project. The operator does not support namespace scoping and must be installed as cluster-wide resource.
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-mongodb-enterprise-catalog-subscription
        namespace: openshift-operators
      spec:
        channel: stable
        name: mongodb-enterprise
        installPlanApproval: Automatic
        source: ibm-mongodb-enterprise-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.
      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n openshift-operators ibm-mongodb-enterprise-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns mongodb-enterprise.v1.10.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n openshift-operators mongodb-enterprise.v1.10.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n openshift-operators -l olm.owner="mongodb-enterprise.v1.10.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. Create the MongoDB (Cloud Pak for Data) operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-cpd-mongodb-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: stable
        name: ibm-cpd-mongodb
        installPlanApproval: Automatic
        source: ibm-cpd-mongodb-catalog
        sourceNamespace: openshift-marketplace
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-mongodb-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-mongodb.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-mongodb.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-mongodb.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-cpd-openpages-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        installPlanApproval: Automatic
        name: ibm-cpd-openpages-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-openpages-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-openpages-operator.v8.203.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-openpages-operator.v8.203.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-openpages-operator.v8.203.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. If you want OpenPages to automatically provision a Db2 database, you must also create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2aaservice-catalog-subscription
        generation: 1
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-db2aaservice-cp4d-operator
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
        startingCSV: ibm-db2aaservice-cp4d-operator.v1.0.1
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2aaservice-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-db2aaservice-cp4d-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-db2aaservice-cp4d-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-db2aaservice-cp4d-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-cpd-openpages-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        installPlanApproval: Automatic
        name: ibm-cpd-openpages-operator
        source: ibm-cpd-openpages-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-openpages-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-openpages-operator.v8.203.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-openpages-operator.v8.203.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-openpages-operator.v8.203.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    3. If you want OpenPages to automatically provision a Db2 database, you must also create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-db2aaservice-catalog-subscription
        generation: 1
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-db2aaservice-cp4d-operator
        installPlanApproval: Automatic
        source: ibm-db2aaservice-cp4d-operator-catalog
        sourceNamespace: openshift-marketplace
        startingCSV: ibm-db2aaservice-cp4d-operator.v1.0.1
      EOF
    4. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-db2aaservice-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-db2aaservice-cp4d-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-db2aaservice-cp4d-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-db2aaservice-cp4d-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-planning-analytics-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-planning-analytics-operator
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-planning-analytics-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-planning-analytics-operator.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-planning-analytics-operator.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-planning-analytics-operator.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-planning-analytics-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-planning-analytics-operator
        installPlanApproval: Automatic
        source: ibm-planning-analytics-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-planning-analytics-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-planning-analytics-operator.v4.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-planning-analytics-operator.v4.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-planning-analytics-operator.v4.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-productmaster-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: alpha
        name: ibm-cpd-productmaster
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-productmaster-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-productmaster.v1.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-productmaster.v1.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-productmaster.v1.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-productmaster-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: alpha
        name: ibm-cpd-productmaster
        installPlanApproval: Automatic
        source: ibm-productmaster-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-productmaster-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-productmaster.v1.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-productmaster.v1.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-productmaster.v1.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-rstudio-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-rstudio-operator
          app.kubernetes.io/name: ibm-cpd-rstudio-operator-catalog-subscription
        name: ibm-cpd-rstudio-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.0
          installPlanApproval: Automatic
          name: ibm-cpd-rstudio
          source: ibm-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-rstudio-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-rstudio.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-rstudio.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-rstudio.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-rstudio-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-rstudio-operator
          app.kubernetes.io/name: ibm-cpd-rstudio-operator-catalog-subscription
        name: ibm-cpd-rstudio-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.0
          installPlanApproval: Automatic
          name: ibm-cpd-rstudio
          source: ibm-cpd-rstudio-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-rstudio-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-rstudio.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-rstudio.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-rstudio.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-spss-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-spss-operator
          app.kubernetes.io/name: ibm-cpd-spss-operator-catalog-subscription
        name: ibm-cpd-spss-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.0
          installPlanApproval: Automatic
          name: ibm-cpd-spss
          source: ibm-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-spss-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-spss.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-spss.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-spss.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-spss-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-spss-operator
          app.kubernetes.io/name: ibm-cpd-spss-operator-catalog-subscription
        name: ibm-cpd-spss-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.0
          installPlanApproval: Automatic
          name: ibm-cpd-spss
          source: ibm-cpd-spss-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-spss-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-spss.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-spss.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-spss.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-voice-gateway-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-voice-gateway-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-voice-gateway-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-voice-gateway-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-voice-gateway-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-voice-gateway-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-voice-gateway-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        name: ibm-voice-gateway-operator
        source: ibm-voice-gateway-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-voice-gateway-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-voice-gateway-operator.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-voice-gateway-operator.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-voice-gateway-operator.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-watson-assistant-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v4.0
        name: ibm-watson-assistant-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-assistant-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-watson-assistant-operator.v4.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-watson-assistant-operator.v4.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-watson-assistant-operator.v4.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-watson-assistant-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v4.0
        name: ibm-watson-assistant-operator
        source: ibm-watson-assistant-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-assistant-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-watson-assistant-operator.v4.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-watson-assistant-operator.v4.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-watson-assistant-operator.v4.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Watson Assistant for Voice Interaction is comprised of the following services:
    • Voice Gateway
    • Watson Assistant
    • Watson Speech to Text
    • Watson Text to Speech
  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-watson-discovery-operator-subscription
          app.kubernetes.io/managed-by: ibm-watson-discovery-operator
          app.kubernetes.io/name: ibm-watson-discovery-operator-subscription
        name: ibm-watson-discovery-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v4.0
        name: ibm-watson-discovery-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-discovery-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-watson-discovery-operator.v4.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-watson-discovery-operator.v4.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-watson-discovery-operator.v4.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-watson-discovery-operator-subscription
          app.kubernetes.io/managed-by: ibm-watson-discovery-operator
          app.kubernetes.io/name: ibm-watson-discovery-operator-subscription
        name: ibm-watson-discovery-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v4.0
        name: ibm-watson-discovery-operator
        source: ibm-watson-discovery-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-discovery-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-watson-discovery-operator.v4.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-watson-discovery-operator.v4.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-watson-discovery-operator.v4.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Specialized installations only. By default, IBM Cloud Pak foundational services expects that the Db2U operator (ibm-db2u-operator) is installed in the ibm-common-services project. However, if you are using the specialized installation architecture (where the IBM Cloud Pak foundational services operators and Cloud Pak for Data operators are in separate OpenShift projects), you must edit the IBM Cloud Pak foundational services operand registry to point to the project where the Cloud Pak for Data operators are installed:
      1. Run the following command to edit the IBM Cloud Pak foundational services operand registry:
        oc edit operandRegistry common-service
      2. Change the value of the namespace entry for the ibm-db2u-operator. Specify the OpenShift project where the Cloud Pak for Data operators are installed, for example, cpd-operators:
         - channel: v1.1
            installPlanApproval: Automatic
            name: ibm-db2u-operator
            namespace: cpd-operators    # Specify the project where the Cloud Pak for Data operators are installed
            packageName: db2u-operator
            scope: public
            sourceName: ibm-db2uoperator-catalog
            sourceNamespace: openshift-marketplace
      3. Save your changes and exit. For example, if you are using vi, hit esc and enter :wq.
    2. Create the Watson Knowledge Catalog operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance:  ibm-cpd-wkc-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-wkc-operator
          app.kubernetes.io/name:  ibm-cpd-wkc-operator-catalog-subscription
        name: ibm-cpd-wkc-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.0
          installPlanApproval: Automatic
          name: ibm-cpd-wkc
          source: ibm-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    3. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-wkc-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wkc.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wkc.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wkc.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Specialized installations only. By default, IBM Cloud Pak foundational services expects that the Db2U operator (ibm-db2u-operator) is installed in the ibm-common-services project. However, if you are using the specialized installation architecture (where the IBM Cloud Pak foundational services operators and Cloud Pak for Data operators are in separate OpenShift projects), you must edit the IBM Cloud Pak foundational services operand registry to point to the project where the Cloud Pak for Data operators are installed:
      1. Run the following command to edit the IBM Cloud Pak foundational services operand registry:
        oc edit operandRegistry common-service
      2. Change the value of the namespace entry for the ibm-db2u-operator. Specify the OpenShift project where the Cloud Pak for Data operators are installed, for example, cpd-operators:
         - channel: v1.1
            installPlanApproval: Automatic
            name: ibm-db2u-operator
            namespace: cpd-operators    # Specify the project where the Cloud Pak for Data operators are installed
            packageName: db2u-operator
            scope: public
            sourceName: ibm-db2uoperator-catalog
            sourceNamespace: openshift-marketplace
      3. Save your changes and exit. For example, if you are using vi, hit esc and enter :wq.
    2. Create the Watson Knowledge Catalog operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance:  ibm-cpd-wkc-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-wkc-operator
          app.kubernetes.io/name:  ibm-cpd-wkc-operator-catalog-subscription
        name: ibm-cpd-wkc-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.0
          installPlanApproval: Automatic
          name: ibm-cpd-wkc
          source: ibm-cpd-wkc-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    3. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-wkc-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wkc.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wkc.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wkc.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-wml-operator-subscription
          app.kubernetes.io/managed-by: ibm-cpd-wml-operator
          app.kubernetes.io/name: ibm-cpd-wml-operator-subscription
        name: ibm-cpd-wml-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.1
          installPlanApproval: Automatic
          name: ibm-cpd-wml-operator
          source: ibm-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-wml-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wml-operator.v1.1.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wml-operator.v1.1.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wml-operator.v1.1.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-wml-operator-subscription
          app.kubernetes.io/managed-by: ibm-cpd-wml-operator
          app.kubernetes.io/name: ibm-cpd-wml-operator-subscription
        name: ibm-cpd-wml-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
          channel: v1.1
          installPlanApproval: Automatic
          name: ibm-cpd-wml-operator
          source: ibm-cpd-wml-operator-catalog
          sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-wml-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wml-operator.v1.1.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wml-operator.v1.1.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wml-operator.v1.1.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-cpd-wml-accelerator-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        name: ibm-cpd-wml-accelerator-operator
        channel: WML-Accelerator-2.3
        installPlanApproval: Automatic
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-wml-accelerator-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wml-accelerator-operator.v2.3.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wml-accelerator-operator.v2.3.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wml-accelerator-operator.v2.3.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-cpd-wml-accelerator-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        name: ibm-cpd-wml-accelerator-operator
        channel: WML-Accelerator-2.3
        installPlanApproval: Automatic
        source: ibm-cpd-wml-accelerator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-wml-accelerator-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wml-accelerator-operator.v2.3.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wml-accelerator-operator.v2.3.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wml-accelerator-operator.v2.3.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-watson-openscale-operator-subscription
        labels:
          app.kubernetes.io/instance: ibm-watson-openscale-operator-subscription
          app.kubernetes.io/managed-by: ibm-watson-openscale-operator
          app.kubernetes.io/name: ibm-watson-openscale-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1
        installPlanApproval: Automatic
        name: ibm-cpd-wos
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-openscale-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wos.v1.1.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wos.v1.1.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wos.v1.1.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-watson-openscale-operator-subscription
        labels:
          app.kubernetes.io/instance: ibm-watson-openscale-operator-subscription
          app.kubernetes.io/managed-by: ibm-watson-openscale-operator
          app.kubernetes.io/name: ibm-watson-openscale-operator-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1
        installPlanApproval: Automatic
        name: ibm-cpd-wos
        source: ibm-openscale-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-openscale-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wos.v1.1.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wos.v1.1.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wos.v1.1.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment.

    Important: The same operator subscription is used for Watson Speech to Text and Watson Text to Speech. If you plan to install both services, you only need to create the subscription once.
    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-watson-speech-operator-subscription
        namespace: ibm-common-services  # Pick the project that contains the Cloud Pak for Data operator: ibm-common-services (default) or cpd-operators
      spec:
        channel: v4.0
        name: ibm-watson-speech-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-speech-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-watson-speech-operator.v4.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-watson-speech-operator.v4.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-watson-speech-operator.v4.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-watson-speech-operator-subscription
        namespace: ibm-common-services  # Pick the project that contains the Cloud Pak for Data operator: ibm-common-services (default) or cpd-operators
      spec:
        channel: v4.0
        name: ibm-watson-speech-operator
        source: ibm-watson-speech-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-speech-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-watson-speech-operator.v4.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-watson-speech-operator.v4.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-watson-speech-operator.v4.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        annotations:
        name: ibm-cpd-ws-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v2.0
        installPlanApproval: Automatic
        name: ibm-cpd-wsl
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-ws-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wsl.v2.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wsl.v2.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wsl.v2.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        annotations:
        name: ibm-cpd-ws-operator-catalog-subscription
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v2.0
        installPlanApproval: Automatic
        name: ibm-cpd-wsl
        source: ibm-cpd-ws-operator-catalog
        sourceNamespace: openshift-marketplace
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-ws-operator-catalog-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-wsl.v2.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-wsl.v2.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-wsl.v2.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment:

    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-ws-runtimes-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-ws-runtimes-operator
          app.kubernetes.io/name: ibm-cpd-ws-runtimes-operator
        name: ibm-cpd-ws-runtimes-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        installPlanApproval: Automatic
        name: ibm-cpd-ws-runtimes
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
        startingCSV: ibm-cpd-ws-runtimes.v1.0.1
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-ws-runtimes-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-ws-runtimes.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-ws-runtimes.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-ws-runtimes.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        labels:
          app.kubernetes.io/instance: ibm-cpd-ws-runtimes-operator-catalog-subscription
          app.kubernetes.io/managed-by: ibm-cpd-ws-runtimes-operator
          app.kubernetes.io/name: ibm-cpd-ws-runtimes-operator
        name: ibm-cpd-ws-runtimes-operator
        namespace: ibm-common-services|cpd-operators    # Pick the project that contains the Cloud Pak for Data operator
      spec:
        channel: v1.0
        installPlanApproval: Automatic
        name: ibm-cpd-ws-runtimes
        source: ibm-cpd-ws-runtimes-operator-catalog
        sourceNamespace: openshift-marketplace
        startingCSV: ibm-cpd-ws-runtimes.v1.0.1
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-cpd-ws-runtimes-operator \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-cpd-ws-runtimes.v1.0.1.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-cpd-ws-runtimes.v1.0.1 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-cpd-ws-runtimes.v1.0.1" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

  • Create the appropriate operator subscription for your environment.

    Important: The same operator subscription is used for Watson Speech to Text and Watson Text to Speech. If you plan to install both services, you only need to create the subscription once.
    Image location Required subscriptions
    IBM Entitled Registry If you are pulling images from the publicly available registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-watson-speech-operator-subscription
        namespace: ibm-common-services  # Pick the project that contains the Cloud Pak for Data operator: ibm-common-services (default) or cpd-operators
      spec:
        channel: v4.0
        name: ibm-watson-speech-operator
        source: ibm-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-speech-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-watson-speech-operator.v4.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-watson-speech-operator.v4.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-watson-speech-operator.v4.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.

    Private container registry If you are pulling images from a private container registry:
    1. Create the following operator subscription. (Ensure that you update the namespace parameter to specify the correct Red Hat OpenShift project.)
      cat <<EOF |oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: ibm-watson-speech-operator-subscription
        namespace: ibm-common-services  # Pick the project that contains the Cloud Pak for Data operator: ibm-common-services (default) or cpd-operators
      spec:
        channel: v4.0
        name: ibm-watson-speech-operator
        source: ibm-watson-speech-operator-catalog
        sourceNamespace: openshift-marketplace
        installPlanApproval: Automatic
      EOF
    2. Validate that the operator was successfully created.

      For each command, ensure that you specify the appropriate Red Hat OpenShift project (either ibm-common-services or cpd-operators) for the --namespace (-n) argument.

      1. Run the following command to confirm that the subscription was triggered:
        oc get sub -n operator-project ibm-watson-speech-operator-subscription \
        -o jsonpath='{.status.installedCSV} {"\n"}'

        Verify that the command returns ibm-watson-speech-operator.v4.0.0.

      2. Run the following command to confirm that the cluster service version (CSV) is ready:
        oc get csv -n operator-project ibm-watson-speech-operator.v4.0.0 \
        -o jsonpath='{ .status.phase } : { .status.message} {"\n"}'

        Verify that the command returns Succeeded : install strategy completed with no errors.

      3. Run the following command to confirm that the operator is ready:
        oc get deployments -n operator-project -l olm.owner="ibm-watson-speech-operator.v4.0.0" \
        -o jsonpath="{.items[0].status.availableReplicas} {'\n'}"

        Verify that the command returns an integer greater than or equal to 1. If the command returns 0, wait for the deployment to become available.