Helm Values Reference
The nvca-operator Helm chart is configured through a standard Helm values file (values.yaml)
passed to helm upgrade -f values.yaml. This page documents all available parameters.
The parameters listed below are a snapshot and may not reflect the latest chart version.
Always refer to the values.yaml and values.schema.json included in your chart
version for the authoritative list of parameters and defaults:
How Values Are Structured
The chart values are organized into three layers:
-
Shared parameters (top-level) — Apply to all deployment modes. These control the operator image, NGC authentication, node placement, network policies, observability, agent resources, and agent runtime config. Examples:
image,ngcConfig,nodeSelector,networkPolicy,agent,agentConfig. -
helmManaged.*— Only used whenngcConfig.clusterSourceis"helm-managed". These define the cluster identity and backend configuration that would otherwise come from the NGC UI. Includes cloud provider, region, cluster group, NVCA version, feature gates, cluster attributes, and manual GPU config.
The key field is ngcConfig.clusterSource:
"ngc-managed"(default) — The operator fetches cluster configuration from the NGC control plane. ThehelmManagedandselfManagedsections are ignored."helm-managed"— The operator reads backend configuration fromhelmManaged.*values.
Shared Parameters
These parameters apply to all deployment modes.
NVCA Operator
NGC Authentication
Node Selector
Network Policies
OpenTelemetry
Agent Configuration
Helm-Managed Parameters
Only used when ngcConfig.clusterSource: "helm-managed".
Related Documentation
- NVCA Configuration — how to use these values to configure specific features (caching, network policies, manual instance config, etc.)
- Helm-Managed Clusters — switching to and from helm-managed mode
- Agent config merging — using
agentConfig.mergeConfigfor runtime config overrides