NIM Service Chart
Overview
The nvidia-lipsync-h4m-service Helm chart deploys the NVIDIA LipSync NIM as a standalone inference service on Kubernetes or Red Hat OpenShift.
This chart can be deployed standalone for integration into a custom media pipeline, or as a subchart of the End-to-End Demo Chart.
Installation
Prerequisites
Complete all prerequisite steps (Rivermax license, image pull and model pull secrets, GPU node, Multus attachment for SMPTE ST 2110) before running helm install. For details, refer to Getting Started.
For hardware requirements per pod, refer to the Support Matrix.
If not already done, add the Helm repository and pull the chart. (For the full repository setup, refer to Pull Helm Charts.)
The downloaded .tgz is referenced directly in the following installation commands.
Helm Installation
The chart includes a default values.yaml. For full SMPTE ST 2110 and NMOS override files, refer to Starter Configuration Files.
Default deployment (NMOS mode, 1080p):
The default values.yaml ships with example values for cluster-specific fields such as node selector (example-gpu-node), image pull secret, network name, and scheduler. You must update these values to match your cluster before deploying.
With inline overrides:
Common --set overrides:
After installation, check pod status:
On Red Hat OpenShift, replace kubectl with oc.
Example output:
Confirm the LipSync NIM pod shows 1/1 in the READY column before continuing.
For NMOS, refer to Chrome Remote Desktop for UI access and setup steps.
For NMOS connection order and NMOS known issues, refer to Limitations and Known Behaviors.
Deployment Modes
The NIM service offers two modes to support media stream connections:
SMPTE ST 2110 Mode
NMOS discovery is disabled. All multicast IP addresses, ports, and session parameters must be configured explicitly. Sender output IP addresses and ports must match NIM service input IP addresses and ports, and NIM service output IP addresses and ports must match downstream receiver input IP addresses and ports.
NMOS Mode
Stream connections are managed via the NMOS Connection Manager UI. Most input and output transport parameters can be omitted from the values file—only session names and ancillary output parameters must be set. On Holoscan for Media clusters, the UI is typically opened from a browser on the cluster network; for remote graphical access, refer to Chrome Remote Desktop in Getting Started.
For NMOS connection order and other known issues, refer to Limitations and Known Behaviors.
Starter Configuration Files
Copy the appropriate configuration into values-st2110.yaml or values-nmos.yaml, adjust fields for your environment, and pass it to helm upgrade --install with -f.
For a full reference of all Helm keys and pipeline tuning parameters, refer to the Configuration Reference.
ST 2110 (Static Mode) Configuration (values-st2110.yaml)
values-st2110.yaml (ST 2110, NMOS disabled):
NMOS Configuration (values-nmos.yaml)
On Red Hat OpenShift, replace kubectl with oc. For log access, refer to Observability.
Verify and Check Logs
Uninstall
For troubleshooting and advanced configuration, refer to Advanced Usage.