Common Helm Configuration
This page covers Helm values that apply to any Studio Voice NIM service chart deployment. The same keys appear under nvidia-studio-voice-h4m-service.<key> when the NIM is deployed as part of the end-to-end demo chart.
Global Overrides
Both the NIM service chart and the end-to-end sample (umbrella) chart expose a global section. When a global value is non-empty, it overrides the corresponding per-component key for all subcharts (sender, receiver, and NIM service). Leave a value as "" to use each component’s own setting instead.
Use global values when deploying the umbrella chart so that node selector, pull secret, network, and scheduler need to be specified only once instead of per component.
Cluster and Workload
NGC and Model Download
Model Cache and Logs PVCs
Subkeys: enabled, create, size, storageClassName, mountPath, readOnly, subPath. For configuration examples, refer to Advanced Usage.
NMOS
NMOS HTTP port 9010 and the Multus network attachment media-a-tx-net are often set in chart templates—confirm for your chart version.
Service Endpoints
The NIM service chart and umbrella sample chart create a Kubernetes Service for each component that exposes the NMOS Node API (IS-04/IS-05) on port 9010. Use these to reach the NMOS Connection Manager from outside the pod without kubectl port-forward.
In the umbrella sample chart, the same keys apply per-component under sender.service.*, receiver.service.*, and nvidia-studio-voice-h4m-service.service.*. The Service name is <appName>-endpoint.
Note that the NIM HTTP API endpoints described in Observability (port 8000, /v1/health/*, /v1/metrics, and so on) are exposed inside the container and require kubectl port-forward for external access; they are not fronted by the chart-managed Service.
See Also
- Configuration Reference
- Pipeline Configuration — Studio Voice tuning, model configuration, ST 2110 sessions.
- Getting Started — Secret creation and high-speed network setup.