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 system:admin

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 that resembles 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 that resembles 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: embedded 2
        source: redhat-operators
        sourceNamespace: openshift-marketplace

      1

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

      2

      Version 2.1 of the Red Hat OpenShift Data Science Operator is available through a channel called embedded.

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

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

      You see output that resembles 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.

   The OperatorHub page opens.

3. 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.

   The Install Operator page opens.

6. For Update channel, select embedded.

   Note

   Version 2.1 of the Red Hat OpenShift Data Science Operator is available through a channel called embedded.

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.

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 system:admin

3. Optional: If you created a DataScienceCluster object to install OpenShift Data Science components, delete the DataScienceCluster object.

   $ oc delete datasciencecluster $(oc get datasciencecluster --no-headers |  awk '{print $1}')

   You see output that resembles the following:

   datasciencecluster.datasciencecluster.opendatahub.io "default" deleted

   Note

   Deleting the DataScienceCluster object also deletes the pods for any OpenShift Data Science components that you installed. This removes the OpenShift Data Science components.

4. Delete the DSCInitialization object that the Operator created during installation.

   $ oc delete dscinitialization $(oc get dscinitialization --no-headers |  awk '{print $1}')

   You see the following output:

   dscinitialization.dscinitialization.opendatahub.io "default" deleted

5. Delete the Subscription object that you created to install the Operator.

   $ oc delete subscription <subscription_name> -n <namespace_name>

   In the following example, the command shown deletes the rhods-operator subscription from the redhat-ods-operator namespace:

   $ oc delete subscription rhods-operator -n redhat-ods-operator

   You see output that resembles the following:

   subscription.operators.coreos.com "rhods-operator" deleted

6. Navigate to the directory that contains the YAML file you used to create a namespace to install the Operator.

7. Delete the namespace that you created to install the Operator.

   $ oc delete -f <namespace_file_name>.yaml

   You see output that resembles the following:

   namespace "redhat-ods-operator" deleted

   Note

   Deleting the namespace also deletes the OperatorGroup object that you created during installation of the Operator.

8. Delete the namespaces that the Operator created during installation.

   $ oc delete ns -l opendatahub.io/generated-namespace

   For the default Operator installation, you see the following output:

   namespace "redhat-ods-applications" deleted
   namespace "redhat-ods-monitoring" deleted

   Note

   If you installed the workbenches component of OpenShift Data Science, the preceding command also deletes the rhods-notebooks namespace created during that installation.

Procedure

1. Open a new terminal window.

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

   $ oc login <openshift_cluster_url> -u system:admin

3. Create a DataScienceCluster object custom resource (CR) file, for example, rhods-operator-dsc.yaml.

   apiVersion: datasciencecluster.opendatahub.io/v1
   kind: DataScienceCluster
   metadata:
     name: default
   spec:
     components:
       codeflare:
         managementState: "Removed"
       dashboard:
         managementState: "Removed"
       datasciencepipelines:
         managementState: "Removed"
       kserve:
         managementState: "Removed"
       modelmeshserving:
         managementState: "Removed"
       ray:
         managementState: "Removed"
       workbenches:
         managementState: "Removed"

4. In the spec.components section of the CR, for each OpenShift Data Science component shown, set the value of the managementState field to either Managed or Removed. These values are defined as follows:

   Managed

   The Operator actively manages the component, installs it, and tries to keep it active. The Operator will upgrade the component only if it is safe to do so.

   Removed

   The Operator actively manages the component but does not install it. If the component is already installed, the Operator will try to remove it.

5. Create the DataScienceCluster object in your OpenShift Container Platform cluster to install the specified OpenShift Data Science components.

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

   You see output that resembles the following:

   datasciencecluster.datasciencecluster.opendatahub.io/default created

Procedure

1. Log in to the OpenShift Container Platform web console as a cluster administrator.

2. In the web console, click Operators → Installed Operators and then click the Red Hat OpenShift Data Science Operator.

   The Operator details page opens.

3. Create a DataScienceCluster object to install OpenShift Data Science components by performing the following actions:

   1. Click the Data Science Cluster tab.
   2. Click Create DataScienceCluster.

   3. For Configure via, select YAML view.

      An embedded YAML editor opens showing a default custom resource (CR) for the DataScienceCluster object.

   4. In the spec.components section of the CR, for each OpenShift Data Science component shown, set the value of the managementState field to either Managed or Removed. These values are defined as follows:

      Managed

      The Operator actively manages the component, installs it, and tries to keep it active. The Operator will upgrade the component only if it is safe to do so.

      Removed

      The Operator actively manages the component but does not install it. If the component is already installed, the Operator will try to remove it.

4. Click Create.

   The Data Science Cluster tab reopens.