chore(deps): update nvidia-device-plugin (patch)

[renovate]

This PR contains the following updates:

Package	Update	Change
nvidia-device-plugin	patch	0.19.2-2.azl3 → 0.19.2-3.azl3
nvidia-device-plugin	patch	0.19.2-ubuntu24.04u2 → 0.19.2-ubuntu24.04u3
nvidia-device-plugin	patch	0.19.2-ubuntu22.04u2 → 0.19.2-ubuntu22.04u3

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[aks-node-assistant]

🕵️ AgentBaker Linux Gate Detective — Build 167866855 (Run AgentBaker E2E) FAILED — known shared-cluster infra outage, not caused by this PR.

TL;DR

Matches existing wiki signature kubenet-v5-node-not-ready-scriptless on shared westus3 cluster abe2e-azure-networkisolated-v3-d6cc9 (with kubenet-v5-150ee also affected). Repair item #38403603 is already tracking this fleet/apiserver issue. This PR is a Renovate patch bump for nvidia-device-plugin — a sidecar image bump that cannot affect kubelet registration on the data-plane VMSS.

3-level RCA

1. Surface symptom — 210 failures in Run AgentBaker E2E; every failed scenario terminates at kube.go:195 🔴 FAIL: "<vmss>" haven't appeared in k8s API server: context deadline exceeded after ~857s on shared cluster abe2e-azure-networkisolated-v3-d6cc9 (rg abe2e-westus3).

2. Corroboration — Same pattern simultaneously reproduced this hour on PRs #8600, #8294, #8509 (other Renovate dependency bumps) all hitting the same two shared clusters in westus3 — 4 unrelated PRs failing identically within ~7 minutes of each other is a textbook infra-outage fingerprint.

3. Root-cause challenge — Strongest alternative: PR-caused regression via the new nvidia-device-plugin image. Why less likely: the bump is a DaemonSet container image patch (GPU plugin) that runs on GPU nodes only; non-GPU scenarios fail equally, and the failure point is pre-kubelet-registration. No path from a container-image tag change to apiserver throttling on a shared cluster.

Classification

• Test infrastructure / shared-cluster fleet stress (not PR-caused)
• Wiki signature: kubenet-v5-node-not-ready-scriptless (Count → 16 distinct builds incl. this one)
• Confidence: High infra outage; High PR is unrelated.

Recommended next action

• For this PR: rerun the gate once shared clusters recover; no code change required.
• Owner of the underlying issue: AgentBaker E2E test-infra (repair item #38403603).

Evidence

• Failed run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=167866855
• Failed job: Run AgentBaker E2E (e2e stage)
• Test summary: 414 tests, 97 skipped, 210 failures in 3565.6s
• Teams escalation thread: WS - CI - CD - E2E - CVE

Posted by Clawpilot AgentBaker Linux Gate Detective Watcher.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.