Is the NVIDIADriver CRD (manager and startupProbe fields) merged with the default?

[skirsten]

Nowhere does it mention what happens to fields such as manager in the NVIDIADriver CRD if its empty.

In the docs and examples an empty object is provided:

manager: {}

But the "default" NVIDIADriver includes the whole definition for the manager as well as startupProbe:

manager: 
  env:
  - name: ENABLE_GPU_POD_EVICTION
    value: "true"
  - name: ENABLE_AUTO_DRAIN
    value: "false"
  - name: DRAIN_USE_FORCE
    value: "false"
  - name: DRAIN_POD_SELECTOR_LABEL
    value: ""
  - name: DRAIN_TIMEOUT_SECONDS
    value: 0s
  - name: DRAIN_DELETE_EMPTYDIR_DATA
    value: "false"
  image: k8s-driver-manager
  imagePullPolicy: IfNotPresent
  repository: nvcr.io/nvidia/cloud-native
  version: v0.6.5
startupProbe: 
  failureThreshold: 120
  initialDelaySeconds: 60
  periodSeconds: 10
  timeoutSeconds: 60

I really don't want to have this in the CRD and have to update it so I am hoping that if the manager and startupProbe is not provided (or empty) it will default to that. Can somebody confirm or deny this?

[shivamerla]

@skirsten your understanding is correct. Driver manager image is set as an env by default with the operator deployment.

        - name: "DRIVER_MANAGER_IMAGE"
          value: "nvcr.io/nvidia/cloud-native/k8s-driver-manager:v0.6.2"

So, this need not be specified in each NVIDIADriver instance.