Skip to main contentElyra

Deploying Open Data Hub with Elyra

This document outlines how to perform a quick deployment of Kubeflow, JupyterHub and Elyra on Open Data Hub (ODH) using the Open Data Hub Operator.

Note the following:

  • The instructions in this document utilize default configurations, which are unlikely to meet the requirements of a production deployment.
  • By completing the steps in this document Kubeflow 1.3, JupyterHub v1.4, and Elyra v2.2.4 are deployed in the kubeflow project/namespace.
  • The Kubeflow Central dashboard is unsecured.
  • The JupyterHub GUI is secured by OpenShift.

Requirements

Verify that the following requirements are met.

  • Access to a v4.x Red Hat OpenShift Cluster (16 GB RAM, 6 CPUs, and 45G of disk space) with internet connectivity.
  • The OpenShift CLI (oc) is installed locally.

Prepare for deployment

  1. Open the OpenShift web console in a browser and log in.

  2. Copy the login command.

    Get oc login command

  3. Open a terminal window and run the copied command.

    $ oc login --token=TOKEN_VAL --server=https://SERVER:PORT

  4. Create a new project named kubeflow. 

    $ oc new-project kubeflow

  5. Verify that the CLI is using the new kubeflow project.

    $ oc project kubeflow

  6. Keep the terminal window open.

Install the Open Data Hub Project Operator on OpenShift

The Open Data Hub Project Operator manages installation, configuration, and the lifecycle of Open Data Hub projects. The operator is available on OpenShift OperatorHub as a community operator.

To install the operator:

  1. Open the OpenShift web console and log in.
  2. Switch to the Administrator view.
  3. Open the projects list (Home > Projects). Open project list in OpenShift
  4. Switch to the kubeflow project. Open kubeflow project
  5. Open the Operator Hub page (Operators > OperatorHub).
  6. Search for the Open Data Hub operator. Install ODH operator
  7. Install the operator, keeping the default values.
  8. Navigate to Operators > Installed Operators and wait for the operator installation to complete.

Next, you’ll install Kubeflow using the operator.

Deploy Kubeflow on OpenShift

To deploy Kubeflow using the Open Data Hub operator:

  1. Select the Open Data Hub operator from the list of installed operators.
  2. On the operator details page select the Details tab, if it is not opened by default. Deploy application using ODH operator
  3. Create a new deployment by clicking Create instance.
  4. Select Configure via YAML view.
  5. Remove the default deployment configuration in the editor.
  6. Open this Kubeflow v1.3 deployment file for OpenShift in a new browser tab/window.
  7. Copy and paste the content of this file into the editor. Deploy Kubeflow using ODH operator
  8. Click Create to deploy Kubeflow on the cluster.
  9. In the terminal window monitor the deployment progress by periodically listing pods in the kubeflow namespace. Wait until all pods are running. This might take a couple minutes.
    $ oc get pods --namespace kubeflow
    Upon successful deployment you can access the Kubeflow Central dashboard using a public route.
  10. In the terminal window run the following command to retrieve the public Kubeflow Central dashboard URL:
    $ oc get routes -n istio-system istio-ingressgateway -o jsonpath='http://{.spec.host}'
  11. Open the displayed URL in a web browser to access the Kubeflow Central dashboard.
  12. Do not select a namespace entry, if you’ve deployed Kubeflow using the defaults.

The Kubeflow deployment is complete. As part of this deployment an instance of the MinIO object storage was provisioned.

Next, you’ll create a public endpoint for this service that provides you access to the MinIO GUI.

Expose the MinIO object storage service

Elyra utilizes object storage to persist artifacts during pipeline processing. The MinIO GUI provides a basic GUI that is not exposed publicly by default.

To make the GUI available:

  1. In the terminal window create a public endpoint for the MinIO service that was deployed alongside Kubeflow.

    $ oc create route edge --service=minio-service --namespace=kubeflow --port=9000 --insecure-policy=Redirect

  2. Retrieve the public MinIO URL.

    $ oc get routes -n kubeflow minio-service -o jsonpath='https://{.spec.host}'

  3. Open the displayed URL in a web browser to access the MinIO GUI. Log in using the default credentials (minio/minio123).

    Open MinIO GUI

Note the mlpipeline bucket. This bucket is used by Kubeflow and should not be deleted!

  1. Take note of the following information. You’ll need it later when you create a runtime configuration in Elyra, so that you can run pipelines in this Kubeflow deployment.
    • The MinIO GUI URL (http://minio-service-kubeflow...).
    • The MinIO access key (minio).
    • The MinIO secret key (minio123).

Next, you’ll install JupyterHub with Elyra support.

Deploy JupyterHub (with Elyra) on OpenShift

In Open Data Hub, notebooks are served using JupyterHub. The default deployment includes a container image that has JupyterLab with the Elyra extensions pre-installed.

To deploy JupyterHub and its dependencies:

  1. Open the OpenShift web console.

  2. Navigate to Operators > Installed Operators.

  3. Select the Open Data Hub operator from the list of installed operators.

  4. On the operator details page select the Details tab, if it is not opened by default.

  5. Create a new deployment by clicking Create instance.

  6. Select Configure via YAML view.

  7. Remove the default deployment configuration in the editor.

  8. Copy and paste the following deployment configuration into the editor. This minimal configuration installs common ODH options, JupyterHub, and container images that serve Jupyter notebooks. One of these images, which is named s2i-lab-elyra:vX.Y.Z, has JupyterLab with Elyra pre-installed.

    apiVersion: kfdef.apps.kubeflow.org/v1
    kind: KfDef
    metadata:
      annotations:
        kfctl.kubeflow.io/force-delete: 'false'
      name: opendatahub
      namespace: kubeflow
    spec:
      applications:

    Note: Above deployment configuration utilizes version 1.0.11 of the Open Data Hub manifests, which includes Elyra v2.2.4.

    Deploy JupyterHub with Elyra

  9. Click Create and wait for the deployment to complete.

    Deployment completed

Next, you’ll use the JupyterHub spawner to launch Elyra.

Access Elyra using the JupyterHub Spawner page

The JupyterHub instance you’ve deployed includes a container image that has JupyterLab with the Elyra extensions installed.

To run this image:

  1. In the terminal window run this command to retrieve the exposed JupyterHub URL:

    $ oc get routes -n kubeflow jupyterhub -o jsonpath='http://{.spec.host}/'

  2. Open the displayed URL in a browser, and, if required, log in.

  3. On the JupyterHub Spawner page select s2i-lab-elyra:vX.Y.Z as notebook image.

    Select the Elyra notebook image

    Note: The image tag version does not represent the Elyra version.

  4. Once the container image was pulled and the container is running the JupyterLab GUI with the Elyra extensions opens in the browser window.

  5. In the JupyterLab Launcher window navigate to the Other category and open a terminal.

    Open terminal in JupyterLab

  6. Enter elyra-pipeline --version to display the Elyra version:

    Confirm Elyra version

Next, you’ll create a runtime configuration if you already have Kubeflow deployed in this cluster. If you don’t have Kubeflow installed skip the next section.

Create a Kubeflow Pipelines runtime configuration

In Elyra runtime configurations are used to provide the tooling access to external resources where pipelines can be executed.

To create a runtime configuration that allows for running of pipelines on the Kubeflow instance you’ve deployed:

  1. Select the Runtimes tab from the JupyterLab side bar.

    Open runtime configuration list

  2. Click + and New Kubeflow Pipelines runtime.

  3. Enter the following Kubeflow and MinIO configuration information, assuming you’ve performed a Kubeflow quick install using the linked manifest:

    • Name: Local Kubeflow Pipelines

    • Kubeflow Pipelines API Endpoint: the output from command 

      $ oc get routes -n istio-system istio-ingressgateway -o jsonpath='http://{.spec.host}/pipeline'

    • Kubeflow Pipelines User Namespace: leave empty, if Kubeflow deployment defaults were used

    • Kubeflow Pipelines API Endpoint Username: leave empty, if Kubeflow deployment defaults were used

    • Kubeflow Pipelines API Endpoint Password: leave empty, if Kubeflow deployment defaults were used

    • Kubeflow Pipelines Engine: Tekton, if Kubeflow deployment defaults were used

    • Cloud Object Storage Endpoint: the output from command 

      $ oc get routes -n kubeflow minio-service -o jsonpath='https://{.spec.host}'

    • Cloud Object Storage Credentials Secret: leave empty

    • Cloud Object Storage Username: minio if Kubeflow deployment defaults were used, otherwise the appropriate id

    • Cloud Object Storage Password: minio123 if Kubeflow deployment defaults were used, otherwise the appropriate password

    • Cloud Object Storage Bucket Name: elyra-pipeline-storage

  4. Save the runtime configuration.

This concludes the quick deployment and configuration tasks.

Next steps

Additional resources

Previous
Recipes: Deploying Kubeflow Pipelines Locally for Elyra
Next
Recipes: Using Elyra with the Kubeflow Notebook Server