Chapter 5. Installing the Red Hat OpenShift Data Science Operator
This section shows how to install the Red Hat OpenShift Data Science Operator on your OpenShift Container Platform cluster using the command-line interface (CLI) and the OpenShift web console.
If you want to upgrade from version 1 of OpenShift Data Science rather than performing a new installation, see Upgrading from version 1 of OpenShift Data Science.
If your OpenShift cluster uses a proxy to access the Internet, you can configure the proxy settings for the Red Hat OpenShift Data Science Operator. See Overriding proxy settings of an Operator for more information.
5.1. Installing the Red Hat OpenShift Data Science Operator by using the CLI
The following procedure shows how to use the OpenShift command-line interface (CLI) to install the Red Hat OpenShift Data Science Operator on your OpenShift Container Platform cluster. You must install the Operator before you can install OpenShift Data Science components on the cluster.
Prerequisites
- You have a running OpenShift Container Platform cluster, version 4.11 or greater, configured with a default storage class that can be dynamically provisioned.
- You have cluster administrator privileges for your OpenShift Container Platform cluster.
- You have downloaded and installed the OpenShift command-line interface (CLI). See Installing the OpenShift CLI.
Procedure
- Open a new terminal window.
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>
Create a namespace for installation of the Operator by performing the following actions:
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.
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
Create an operator group for installation of the Operator by performing the following actions:
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.
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
Create a subscription for installation of the Operator by performing the following actions:
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
- stable
-
In the
stable
channel, Red Hat provides updates for the Operator approximately every three weeks. Thestable
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, choosestable
. Theembdedded
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.
NoteThe 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, chooseembedded
orstable
, 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.
NoteThe
beta
channel is a legacy channel that will be removed in a future release. Do not select thebeta
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.
- As described in the preceding step, ensure that the subscription channel you specify is appropriate for your organization’s requirements.
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
Verification
In the OpenShift Container Platform web console, click Operators
Installed Operators and confirm that the Red Hat OpenShift Data Science Operator shows one of the following statuses: -
Installing
- installation is in progress; wait for this to change toSucceeded
. This might take several minutes. -
Succeeded
- installation is successful.
-
In the web console, click Home
Projects and confirm that the following project namespaces are visible and listed as Active
:-
redhat-ods-applications
-
redhat-ods-monitoring
-
redhat-ods-operator
-
5.2. Installing the Red Hat OpenShift Data Science Operator by using the web console
The following procedure shows how to use the OpenShift Container Platform web console to install the Red Hat OpenShift Data Science Operator on your cluster. You must install the Operator before you can install OpenShift Data Science components on the cluster.
Prerequisites
- You have a running OpenShift Container Platform cluster, version 4.11 or greater, configured with a default storage class that can be dynamically provisioned.
- You have cluster administrator privileges for your OpenShift Container Platform cluster.
Procedure
- Log in to the OpenShift Container Platform web console as a cluster administrator.
-
In the web console, click Operators
OperatorHub. On the OperatorHub page, locate the Red Hat OpenShift Data Science Operator.
-
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.
-
Scroll through available Operators or type
- Select the Operator to display additional information.
- Read the information about the Operator and click Install.
For Update channel, select
stable
,embedded
, oralpha
. These subscription channels are described as follows:- stable
-
In the
stable
channel, Red Hat provides updates for the Operator approximately every three weeks. Thestable
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, choosestable
. Theembdedded
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.
NoteThe 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, chooseembedded
orstable
, 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.
NoteThe
beta
channel is a legacy channel that will be removed in a future release. Do not select thebeta
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.
-
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. -
For Installed Namespace, select
redhat-ods-operator (Operator recommended)
. -
Under Update approval, select either
Automatic
orManual
. Click Install.
An installation pane opens. When the installation finishes, a check mark appears beside the Operator name in the installation pane.
Verification
In the OpenShift Container Platform web console, click Operators
Installed Operators and confirm that the Red Hat OpenShift Data Science Operator shows one of the following statuses: -
Installing
- installation is in progress; wait for this to change toSucceeded
. This might take several minutes. -
Succeeded
- installation is successful.
-
In the web console, click Home
Projects and confirm that the following project namespaces are visible and listed as Active
:-
redhat-ods-applications
-
redhat-ods-monitoring
-
redhat-ods-operator
-