Chapter 5. Installing the Red Hat OpenShift Data Science Operator

Procedure

1. Open a new terminal window.

2. In the OpenShift command-line interface (CLI), log in to your OpenShift Container Platform cluster as a cluster administrator, as shown in the following example:

   $ oc login <openshift_cluster_url> -u <admin_username> -p <password>

3. Create a namespace for installation of the Operator by performing the following actions:

   1. Create a namespace YAML file, for example, rhods-operator-namespace.yaml.

      apiVersion: v1
      kind: Namespace
      metadata:
        name: redhat-ods-operator 

      1

      1

      redhat-ods-operator is the recommended namespace for the Operator.

   2. Create the namespace in your OpenShift Container Platform cluster.

      $ oc create -f rhods-operator-namespace.yaml

      You see output similar to the following:

      namespace/redhat-ods-operator created

4. Create an operator group for installation of the Operator by performing the following actions:

   1. Create an OperatorGroup object custom resource (CR) file, for example, rhods-operator-group.yaml.

      apiVersion: operators.coreos.com/v1
      kind: OperatorGroup
      metadata:
        name: rhods-operator
        namespace: redhat-ods-operator 

      1

      1

      You must specify the same namespace that you created earlier in this procedure.

   2. Create the OperatorGroup object in your OpenShift Container Platform cluster.

      $ oc create -f rhods-operator-group.yaml

      You see output similar to the following:

      operatorgroup.operators.coreos.com/rhods-operator created

5. Create a subscription for installation of the Operator by performing the following actions:

   1. Create a Subscription object CR file, for example, rhods-operator-subscription.yaml.

      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: rhods-operator
        namespace: redhat-ods-operator 

      1

      
      spec:
        name: rhods-operator
        channel: stable 

      2

      
        source: redhat-operators
        sourceNamespace: openshift-marketplace

      1

      You must specify the same namespace that you created earlier in this procedure.

      2

      For channel, select a value of stable, embedded, or alpha. These subscription channels are described as follows:

      stable

      In the stable channel, Red Hat provides updates for the Operator approximately every three weeks. The stable channel is intended for production use and provides functionally complete, generally available features (in addition to early-access features where noted in the documentation) that are supported with Red Hat production service level agreements (SLAs).

      embedded

      The embedded channel provides updates for products that integrate Red Hat OpenShift Data Science. This includes IBM watsonx.ai. If this specific use case does not apply to your organization, choose stable. The embdedded channel is intended for production use and provides functionally complete, generally available features (in addition to early-access features where noted in the documentation) that are supported with Red Hat production service level agreements (SLAs).

      alpha

      The alpha channel is intended for development use only. The channel provides development builds and early-access features.

      Note

      The development builds and early-access features that the alpha channel provides are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. Early-access features enable customers to test functionality and provide feedback during the development process. For production environments, choose embedded or stable, based on the preceding descriptions.

      For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope. For more information about the support scope of Red Hat Developer Preview features, see Developer Preview Features Support Scope.

      Note

      The beta channel is a legacy channel that will be removed in a future release. Do not select the beta channel for a new installation of the Operator.

      For more information about the lifecycle associated with each of the available subscription channels, see Red Hat OpenShift Data Science self-managed Life Cycle.

   2. As described in the preceding step, ensure that the subscription channel you specify is appropriate for your organization’s requirements.

   3. Create the Subscription object in your OpenShift Container Platform cluster to install the Operator.

      $ oc create -f rhods-operator-subscription.yaml

      You see output similar to the following:

      subscription.operators.coreos.com/rhods-operator created

Procedure

1. Log in to the OpenShift Container Platform web console as a cluster administrator.
2. In the web console, click Operators OperatorHub.

3. On the OperatorHub page, locate the Red Hat OpenShift Data Science Operator.

   1. Scroll through available Operators or type Red Hat OpenShift Data Science into the Filter by keyword box to find the Red Hat OpenShift Data Science Operator.
4. Select the Operator to display additional information.
5. Read the information about the Operator and click Install.

6. For Update channel, select stable, embedded, or alpha. These subscription channels are described as follows:

   stable

   In the stable channel, Red Hat provides updates for the Operator approximately every three weeks. The stable channel is intended for production use and provides functionally complete, generally available features (in addition to early-access features where noted in the documentation) that are supported with Red Hat production service level agreements (SLAs).

   embedded

   The embedded channel provides updates for products that integrate Red Hat OpenShift Data Science. This includes IBM watsonx.ai. If this specific use case does not apply to your organization, choose stable. The embdedded channel is intended for production use and provides functionally complete, generally available features (in addition to early-access features where noted in the documentation) that are supported with Red Hat production service level agreements (SLAs).

   alpha

   The alpha channel is intended for development use only. The channel provides development builds and early-access features.

   Note

   The development builds and early-access features that the alpha channel provides are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. Early-access features enable customers to test functionality and provide feedback during the development process. For production environments, choose embedded or stable, based on the preceding descriptions.

   For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope. For more information about the support scope of Red Hat Developer Preview features, see Developer Preview Features Support Scope.

   Note

   The beta channel is a legacy channel that will be removed in a future release. Do not select the beta channel for a new installation of the Operator.

   For more information about the lifecycle associated with each of the available subscription channels, see Red Hat OpenShift Data Science self-managed Life Cycle.

7. For Installation mode, observe that the only available value is All namespaces on the cluster (default). This installation mode makes the Operator available to all namespaces in the cluster.
8. For Installed Namespace, select redhat-ods-operator (Operator recommended).
9. Under Update approval, select either Automatic or Manual.

10. Click Install.

    An installation pane opens. When the installation finishes, a check mark appears beside the Operator name in the installation pane.