chore(deps): update oss/v2/kubernetes/apiserver-network-proxy/agent docker tag to v0.32.1-7

[renovate]

This PR contains the following updates:

Package	Update	Change
oss/v2/kubernetes/apiserver-network-proxy/agent	patch	v0.32.1-2 → v0.32.1-7

---

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 this update 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.

[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 167836139 (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-kubenet-v5-150ee. Repair item #38403603 already tracking this fleet/apiserver issue. This PR is a Renovate Docker tag bump for oss/v2/kubernetes/apiserver-network-proxy/agent → v0.32.1-7, which does not touch kubelet, CSE, NBC, or any node provisioning path.

3-level RCA

1. Surface symptom — Every failed scenario terminates at:
kube.go:195 🔴 FAIL: "<vmss>" haven't appeared in k8s API server: context deadline exceeded after ~738s, on cluster abe2e-kubenet-v5-150ee (rg abe2e-westus3).

2. Corroboration — Same back-to-back run on main (build 167835297, no PR) reproduces the identical signature on the same shared cluster, with the same abe2e-kubenet-v5-150ee target — independent corroboration that this is shared-cluster apiserver throttling, not anything specific to PR #7906's commit 00d1e47d. Pattern reproduced on 7 unrelated PRs in the last 24h (#8104, #8294, #8509, #8659, #8667, #8694, #8698) plus consecutive TME pipeline (def 451455) builds on a different westus cluster (abe2e-kubenet-v5-e7055).

3. Root-cause challenge — Strongest alternative: PR-caused regression via the new apiserver-network-proxy/agent image. Why less likely: the proxy-agent is a control-plane-side image (HCP), not consumed by the VHD or node CSE; bumping its docker tag in parts/common/components.json cannot affect kubelet's ability to register on the data-plane VMSS. Failure point is pre-kubelet-registration, before any apiserver-network-proxy interaction would matter. Symptom is identical to the main-branch run at the same time on the same cluster — strong infra signal.

Classification

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

Recommended next action

• For this PR: safe to rebase/rerun 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=167836139
• Failed job: Run AgentBaker E2E (e2e stage)
• Parallel main-branch run with same signature: build 167835297
• Source commit: 00d1e47d05cad2b969c8ec06ad73442ceea69a6d
• Teams escalation thread: WS - CI - CD - E2E - CVE

Posted by Clawpilot AgentBaker Linux Gate Detective Watcher.