Kubernetes Operator Chart
Overview
The nvidia-active-speaker-detection-h4m-operator Helm chart installs the Active Speaker Detection Kubernetes operator. The controller watches NvidiaActiveSpeakerDetectionMediaFunction custom resources and reconciles a deployment for the NIM, SDP ConfigMaps (/sdps), and status.
- Operator chart: Deploys only the controller and CRDs. It does not install a
NvidiaActiveSpeakerDetectionMediaFunctioncustom resource or the NIM workload—apply a custom resource after installation to provision the NIM. - Operand: Each custom resource instance drives one NIM workload (video and ancillary output) according to the inputs, outputs, and parameters declared in that resource.
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 more information, refer to Getting Started.
Pull the Chart
If not already done, add the Helm repository and pull the chart:
For the full repository setup, refer to Pull Helm Charts.
Helm Installation
The chart installs the operator deployment and registers the NvidiaActiveSpeakerDetectionMediaFunction CRD. For all available Helm values and --set keys, refer to Operator Configuration.
The chart expects a pre-created image pull secret for nvcr.io (default name ngc-api-key). If your secret names differ, override as follows:
When the defaults match your cluster, you can use the following command:
The model pull secret and node hostname are set on the custom resource, not Helm values (spec.parameters.ngcModelDownload, spec.nodeSelector). Refer to Create the Custom Resource.
Wait for the controller to be ready:
On Red Hat OpenShift, replace kubectl with oc.
Create the Custom Resource
After the operator controller is ready, save a manifest (for example, nim-media-function.yaml) and configure the following areas:
Apply the manifest:
On Red Hat OpenShift, replace kubectl with oc.
Example Manifest
Reference a custom resource with a placeholder node name, ngc-model-pull-api-key for model download, and common video format defaults. The following spec.parameters.resources block below is part of this CR; it sets Kubernetes requests and limits for the operand workload, using the same numeric defaults as the standalone NIM service chart in Pipeline Configuration.
Extended Parameters (Optional)
As needed, you can add optional spec.parameters fields, including resources (CPU, memory, GPU, hugepages), nimLogs / nimModelCache PVC settings, useAudioThresholdToDetectActiveAudioStream, and testFrameOverlayMode. For field-by-field details, refer to Operator Configuration in the configuration reference. For PVC configuration, refer to Advanced Usage.
Verify
After applying the custom resource:
Inspect custom resource status conditions:
Confirm the CRD is installed:
On Red Hat OpenShift, replace kubectl with oc. For log access, see Observability.
Uninstall
First, delete all custom resource instances so the operator can remove the managed deployments and ConfigMaps; then remove the Helm release. Delete the CRD cluster-wide only if coordinated with cluster administrators; it affects all namespaces.
On Red Hat OpenShift, replace kubectl with oc.
For troubleshooting and known limitations, refer to Advanced Usage.
See Also
- Getting Started — NGC authentication, secrets, and prerequisites.
- Installation — Service, operator, and demo chart installation patterns.
- Configuration Reference — Helm values and operator custom resource field reference.