Operator Configuration
This page covers Helm values for the nvidia-active-speaker-detection-h4m-operator chart (controller pod) and fields for the NvidiaActiveSpeakerDetectionMediaFunction custom resource (NIM workload).
Pipeline tuning semantics on the custom resource match the Pipeline Configuration Helm keys.
Operator Helm Chart (nvidia-active-speaker-detection-h4m-operator)
Values for the operator controller pod (not the NIM deployment):
The media function image is configured when the operator is installed, so NvidiaActiveSpeakerDetectionMediaFunction instances managed by an operator use the same validated operator and media-function image combination. This approach ensures 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.
(operator-media-function-cr)=
Custom Resource (NvidiaActiveSpeakerDetectionMediaFunction)
Full YAML example: Example Manifest.
Scheduling and Cluster
Parameters: Network, Resources, Secrets, Security
Pod Resources (spec.parameters.resources)
Parameters: Pipeline Tuning
(parameters-pipeline-asd-tuning-cr)=
Inputs and Outputs
Video Format Subfields
These subfields apply to video input and video output.
frame_rate must be identical for spec.inputs.video_input.format.video and spec.outputs.video_output.format.video. Invalid values are rejected when the CR is applied. The following values are supported:
Use a plain integer string for whole rates and a numerator/denominator string for fractional rates. Always quote the value in YAML so fractions are not interpreted as numbers.
Audio Format Subfields
These subfields apply to each audio_input_n stream.
CR Schema Reference
With the nvidiaactivespeakerdetectionmediafunctions.nvidia.com CRD installed, inspect field types and OpenAPI details from the cluster:
Some validation rules might not appear in kubectl explain output but are still enforced when the CR is applied.
Status Conditions (status.conditions)
Status Overview
The operator reports health using Kubernetes conditions in status.conditions (type, status, reason, message).
A media function is considered healthy and ready when the following are all True:
Provisioned: Deployment and pod are running.Registered: Successfully registered with NMOS / SDP.Configured: Required configuration has been applied.
Important Statuses
When to Alert
Alert if any of these stay False:
ProvisionedRegisteredConfigured
Most important failure reason values:
DeploymentNotAvailableNmosQueryFailed
Connected False is usually informational or transient and can occur when connections are still being established.
Ignore Active and Degraded for now.
Check Status
Use the custom resource metadata.name (not a Pod name).
See Also
- Configuration Reference
- Kubernetes Operator Installation
- Pipeline Configuration — Pipeline tuning Helm key equivalents.