Getting Started
Holoscan for Media
Platform setup, cluster prerequisites, reference applications, deployment, verification, monitoring, application development, troubleshooting, and support for Holoscan for Media are covered in the NVIDIA Holoscan for Media user guide.
Prerequisites
Before proceeding, check the Support Matrix to verify that the required hardware and software are available.
Access NGC and Helm Charts
An NGC account and an NGC API key are required to authenticate the CLI, pull container images and Helm charts from NVIDIA registries, and create cluster pull secrets.
NGC Authentication
Generate an NGC API key at https://org.ngc.nvidia.com/setup/api-keys. Ensure that at least NGC Catalog is selected from the Services Included dropdown.
Export the key:
Log in to the NGC container and Helm registry:
License and Secrets Management
Rivermax License
Rivermax is required by Holoscan for Media applications to comply with SMPTE ST 2110 timing and traffic-flow requirements.
Create a Kubernetes secret from the license file:
On Red Hat OpenShift, replace kubectl with oc.
Image Pull Secret
Create a docker-registry secret so the cluster can pull images from nvcr.io:
Model Pull Secret
Model artifacts are downloaded by the NIM at runtime using an API key carried in a generic secret, separate from the image pull secret:
High-Speed Network Configuration
Set the network attachment name in the Helm values for each component in the pipeline:
Namespace Scope
NetworkAttachmentDefinition resources are namespace-scoped, and Multus looks them up in the same namespace as the pod. Every network attachment referenced by the chart must exist in the namespace where BNR is installed.
Check which network attachments already exist in your deployment namespace:
On Red Hat OpenShift, replace kubectl with oc.
If a referenced network attachment is missing, pod admission fails with an error such as could not find network attachment definition '<namespace>/media-a-tx-net'.
Security Context
To operate correctly, the NIM container requires allowPrivilegeEscalation: true and the following Linux capabilities:
These values are set in the Helm values or in the BNR operator custom resource under spec.parameters.securityContext. For details, refer to Configuration.
OpenShift Security Context Constraint
For Red Hat OpenShift, grant an SCC that allows the following capabilities:
IPC_LOCKNET_RAWSYS_NICEDAC_READ_SEARCHallowPrivilegeEscalation: true
For development clusters, administrators often grant the built-in privileged SCC to the service account used by the release:
Scheduler and NUMA Topology
The chart defaults to schedulerName: topo-aware-scheduler. This keeps the GPU, SR-IOV virtual function, and CPU allocation NUMA-aligned on clusters that enforce the single-numa-node topology manager policy.
To override schedulerName on clusters without a topology-aware scheduler, use the matching knob for your deployment path:
Chrome Remote Desktop
When BNR is deployed with NMOS enabled, streams are connected and managed through the NMOS Connection Manager web UI. On Holoscan for Media clusters, access to that UI typically requires a browser that can reach the cluster network.