Helm Installation Options#
NeMo Microservices Helm Chart provides flexible installation options through the tagging functionality of Helm. This allows you to choose which microservices to install for various AI and machine learning tasks. This page provides a high-level overview of installing the NeMo microservices for various use cases.
Before Installing NeMo Microservices#
Before installing the NeMo microservices, get familiar with common prerequisites and tasks for using the NeMo Microservices Helm Chart at Helm Installation Overview.
Tag-Based Installation#
The tagging option of the NeMo Microservices Helm Chart allows flexible installation of the microservices depending on your use case requirements.
The following commands show how to install the microservices for different use cases using the Helm CLI.
To install the complete platform:
helm install nemo-microservices nmp/nemo-microservices-helm-chart
For more details, refer to Install NeMo Microservices as a Platform.
To install only customizer functionality:
helm install nemo-customizer nmp/nemo-microservices-helm-chart --set tags.platform=false --set tags.customizer=true
For more details, refer to NeMo Customizer Microservice Deployment Guide.
To install only evaluator functionality:
helm install nemo-evaluator nmp/nemo-microservices-helm-chart --set tags.platform=false --set tags.evaluator=true
For more details, refer to Deploy NeMo Evaluator Using Parent Helm Chart.
To install only auditor functionality:
helm install nemo-auditor nmp/nemo-microservices-helm-chart --set tags.platform=false --set tags.auditor=true --set auditor.enabled=true
For more details, refer to Deploy NeMo Auditor Using Parent Helm Chart.
To install only guardrails functionality:
helm install nemo-guardrails nmp/nemo-microservices-helm-chart --set tags.platform=false --set tags.guardrails=true
For more details, refer to NeMo Guardrails Microservice Deployment Guide.
You can also install the microservices by overriding the values in the default values.yaml file of the chart.