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 two layers:
- Shared parameters (top-level) — These control the operator image, authentication,
node placement, network policies, observability, agent resources, and agent runtime config.
Examples:
image,ngcConfig,nodeSelector,networkPolicy,agent,agentConfig. - “selfManaged.*“ — Used when
ngcConfig.clusterSourceis"self-managed". These define the backend configuration including NVCA version, feature gates, cluster attributes, and manual GPU config.
The key field is “ngcConfig.clusterSource“:
"self-managed"— The operator reads backend configuration fromselfManaged.*values.
The helmManaged and selfManaged sections share many of the same fields
(nvcaVersion, featureGateValues, gpuManualInstanceConfigB64,
clusterAttributes). The difference is that helmManaged also requires cluster
identity fields (cloudProvider, clusterRegion, clusterGroupID,
clusterGroupName) that self-managed deployments get from their own control plane.
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".
Self-Managed Parameters
Only used when ngcConfig.clusterSource: "self-managed" (self-hosted NVCF).
The selfManaged and helmManaged sections share the same backend fields. The key
differences are:
selfManageddoes not have cluster identity fields (cloudProvider,clusterRegion,clusterGroupID,clusterGroupName) — these come from the self-hosted control plane.selfManaged.featureGateValuesdefaults to["DynamicGPUDiscovery"]. To disable a feature, remove it from the list (set to[]).helmManaged.featureGateValuesdefaults to[]. To disable a feature, prefix it with-(e.g.,["-DynamicGPUDiscovery"]).
Related Documentation
- NVCA Configuration — how to use these values to configure specific features (caching, network policies, manual instance config, etc.)
- Agent config merging — using
agentConfig.mergeConfigfor runtime config overrides