Deploy NeMo Studio Using Parent Helm Chart#

You can deploy NeMo Studio using the NeMo Microservices Helm Chart. The chart manages all required dependencies automatically.

This guide explains how to deploy NeMo Studio using the NeMo Microservices Helm Chart to set up only the Studio UI and the necessary backend microservices.

Note

By default, the NeMo Microservices Helm Chart enables all the NeMo microservices except NeMo Studio. To enable NeMo Studio, you need to install with the studio tag.


Prerequisites#

  • An NGC API key with the following key permissions: NGC Catalog, NGC Private Registry, and Public API Endpoints.

  • Install NVIDIA GPU Operator.

  • (Optional) An external PostgreSQL database. The NeMo microservices use a PostgreSQL database to store data. Refer to PostgreSQL for more information.


Installation Steps#

  1. Add the NeMo Microservices Helm Chart Helm repository:

    $ helm repo add nmp https://helm.ngc.nvidia.com/nvidia/nemo-microservices \
       --username='$oauthtoken' \
       --password=$NGC_API_KEY
    
    $ helm repo update
    
  2. Create the namespace:

    $ kubectl create namespace nemo
    
  3. Create an image pull secret in the namespace:

    $ kubectl --namespace nemo \
        create secret docker-registry nvcrimagepullsecret \
        --docker-server=nvcr.io \
        --docker-username='$oauthtoken' \
        --docker-password=$NGC_API_KEY
    
  4. Install the chart with the tags.studio set to true to enable NeMo Studio.

    • Full Platform Installation: This option installs the entire NeMo microservices platform, which is the default behavior of the NeMo Microservices Helm Chart, and NeMo Studio. This enables all the features in NeMo Studio.

      $ helm --namespace nemo-studio \
         install nemo-studio \
         nmp/nemo-microservices-helm-chart \
         --set tags.studio=true
      
    • Minimal Installation: This option installs only NeMo Studio and its minimum required dependencies. For more information about the minimum required dependencies installed with this option, refer to Installed Components per Tag. This enables only the core features in NeMo Studio: Projects, Datasets, and Models.

      $ helm --namespace nemo-studio \
         install nemo-studio \
         nmp/nemo-microservices-helm-chart \
         --set tags.studio=true \
         --set tags.platform=false
      

Note

If you are a platform architect, you are responsible for configuring ingress on your Kubernetes cluster for external access to NeMo Studio services and routes. Refer to Ingress Setup for Production Environment for more information.