Operator Configuration
This page covers Helm values for the nvidia-studio-voice-h4m-operator chart (controller pod) and fields for the NvidiaStudioVoiceMediaFunction custom resource (NIM workload).
Pipeline tuning semantics on the custom resource match the Pipeline Configuration Helm keys.
Operator Helm Chart (nvidia-studio-voice-h4m-operator)
Values for the operator controller pod (not the NIM deployment):
The media-function image is configured when the operator is installed, so NvidiaStudioVoiceMediaFunction instances managed by an operator use the same validated operator and media-function image combination. This approach ensures that the operator and workload are always supported together and avoids compatibility issues.
As a result, CRs managed by an operator share the chart-level mediaFunction.image and mediaFunction.imagePullSecrets configured at install time. To run multiple custom resources with different NIM image tags, deploy multiple operators, each configured with its own mediaFunction.image. For more context, refer to Known Limitations.
(operator-media-function-cr)=
Custom Resource (NvidiaStudioVoiceMediaFunction)
Full YAML example: Example Manifest.
Scheduling and Cluster
Parameters: Network, Resources, Secrets, Security
Parameters: CR
Inputs and Outputs
Subfields for format.audio
These subfields apply to audio input and audio output.
See Also
- Configuration Reference
- Kubernetes Operator Installation
- Pipeline Configuration — Pipeline tuning Helm key equivalents.