NVIDIA / gpu-operator / 28416587058

31%

main: 31%

push

github

Restart driver pods in place when driver config is unchanged

A patch chart upgrade can change only cosmetic pod-template metadata
(e.g. the helm.sh/chart label) without changing the driver itself. The
upgrade controller keys on the DaemonSet's controller revision hash, so
such a change still evicts running GPU workloads and drains the node --
for no driver benefit.

Register a RestartOnlyPredicate on the upgrade state manager that
compares DRIVER_CONFIG_DIGEST -- a hash of the install-relevant driver
config, already set on the driver pod template -- between the running
pod and the desired DaemonSet. When the digests match, the node is
cordoned and the driver pod restarted in place, with no workload
eviction or drain; the driver fast-path keeps the kernel modules loaded
across the restart, so running GPU workloads are not disrupted.
Cordoning keeps the node unschedulable if the restart fails, and the
node is uncordoned on success. A missing or differing digest falls back
to the full upgrade flow.

The digest env name and a reader for it live in internal/config beside
the digest definition; the restart-only routing decision lives in
internal/predicates and is registered on the upgrade state manager in
main.go. The RestartOnlyPredicate hook it relies on is provided by
k8s-operator-libs, vendored here at the merged version.

Signed-off-by: Rajath Agasthya <ragasthya@nvidia.com>

34 of 39 new or added lines in 4 files covered. (87.18%)

4057 of 13018 relevant lines covered (31.16%)

0.36 hits per line