NVIDIA / nodewright / 36755566775

83%

Build Type

push

github

Committed by web-flow

Commit Message

fix(operator): apply runtime-required taints onto the live taint list (#699)

* fix(operator): apply runtime-required taints onto the live taint list

HandleAutoTaint and the reboot re-taint in TrackReboots both patched
spec.taints from the pass's cluster-state snapshot. Taints are an atomic
list, so each write replaced the whole list with the snapshot's copy plus
the runtime-required taint: a taint another controller added after the
snapshot (cluster-autoscaler, Karpenter, the cloud provider, GPU Operator)
was deleted, and one it removed was restored. New and rebooting nodes are
exactly when those controllers are busiest.

Both paths now go through addRuntimeRequiredTaint, which, like
removeRuntimeRequiredTaints, re-reads the node inside each conflict retry
and patches under an optimistic lock, so the taint is appended to the
current list. The reboot path applies the taint before the state reset
and leaves the reboot pending if either write fails, so both are retried
together. It now also records the autoTaint annotation, which is
idempotent for nodes that already carry it.

The heavy pass itself no longer changes taints: runtime-required removal
already re-reads in removeRuntimeRequiredTaints, so these were the
remaining writers.

Fixes #447

Signed-off-by: Alex Yuskauskas <ayuskauskas@nvidia.com>

* fix(operator): re-taint a rebooted node before resetting it, without a marker

The reboot re-taint wrote the autoTaint_<key> annotation, so a node
pre-tainted at provisioning gained a marker the operator never earned,
and a DNS-prefixed taint key (which Validate accepts) produced an invalid
annotation name that the apiserver rejects, leaving the reboot pending
and TrackReboots erroring on every pass. Only HandleAutoTaint marks a
node now; the reboot path relies on the marker surviving Reset, as
before.

The taint write also ran after Reset(), so a failure skipped the node
patch but still saved the wiped status. It now runs first: a failure
leaves the no... (continued)

Coverage Stats

30 of 30 new or added lines in 1 file covered. (100.0%)

6 existing lines in 1 file now uncovered.

9353 of 11354 relevant lines covered (82.38%)

7.63 hits per line