# Defaults applied to every variant of the gpu-operator package.
# The variant-specific files (values-passthrough.yaml, values-vgpu.yaml)
# layer on top.
gpu-operator:
  # Upstream chart v26.x flips ccManager.enabled to true and
  # ccManager.defaultMode to "on". On Hopper-class hardware
  # (H100/H200/B100) with Confidential Computing capability this would
  # auto-enable CC mode after a chart upgrade — a non-trivial behavior
  # change. On non-CC-capable GPUs (L40S, A100, T4, …) the DaemonSet
  # deploys, probes the hardware, and no-ops, but it still enters the
  # cluster's resource graph. Pin to false so the default footprint
  # stays as it was on v25.x; users who want CC enable it explicitly.
  ccManager:
    enabled: false
  # Upstream v26.x also flips vgpuDeviceManager.enabled to true. The
  # primary reason this is pinned back to false: the device manager
  # walks /sys/class/mdev_bus/, which does not exist on Ada Lovelace
  # (L4/L40/L40S, …) or Blackwell (B100, …) on the vGPU 17/20 driver
  # branch — it errors with «no parent devices found». Keeping the
  # default-on would crashloop the DaemonSet on any modern GPU.
  # Secondary consideration: in passthrough mode the operator does not
  # apply the nvidia.com/gpu.deploy.vgpu-device-manager=true label, so
  # the DaemonSet would stay at zero pods, but it would still render
  # into the cluster. The vgpu variant explicitly re-affirms this in
  # values-vgpu.yaml.
  vgpuDeviceManager:
    enabled: false