fix(acl): bump marketplace image to 3.20260602.01

[aadhar-agarwal]

Bumps the ACL marketplace image from 3.20260517.01 to 3.20260602.01 for all ACL VHD build jobs in both pipelines (.vsts-vhd-builder.yaml and .vsts-vhd-builder-release.yaml), covering the azure-linux-3-acl (x86) and azure-linux-3-arm64-gen2-acl (arm64) SKUs, FIPS and non-FIPS.

[TEST All VHDs] AKS Linux VHD Build - Msft Tenant - Running

AKS Linux VHD Build - TME Tenant - Passed

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

[Copilot]

Pull request overview

Updates the pinned Azure Container Linux (ACL) Azure Marketplace base image version used by the VHD builder pipelines so ACL VHD build jobs consume the newly published image.

Changes:

• Bump IMG_VERSION for azure-linux-3-acl (x86_64) from 3.20260517.01 → 3.20260602.01 in the main VHD builder pipeline.
• Bump IMG_VERSION for azure-linux-3-arm64-gen2-acl (arm64) from 3.20260517.01 → 3.20260602.01 in the main VHD builder pipeline.
• Apply the same version bumps to the release VHD builder pipeline (covering FIPS and non-FIPS ACL jobs).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.pipelines/.vsts-vhd-builder.yaml	Updates the pinned ACL marketplace IMG_VERSION used by ACL build jobs (x86 and arm64; FIPS/non-FIPS).
.pipelines/.vsts-vhd-builder-release.yaml	Mirrors the same ACL IMG_VERSION bump in the release pipeline jobs.

[aks-node-assistant]

AgentBaker Linux PR gate — 236-failure mass run: shared cluster proxy-pod readiness exhaustion (test-infra, NOT this PR)

• Run: 167393232 (failed)
• Failed task: Run AgentBaker E2E
• Test summary: DONE 402 tests, 95 skipped, 236 failures in 653.724s (~59% failure rate; 0 fwupd hits)

Dominant failure:

prepare cluster tasks: dag execution failed:
waiting for proxy pod to be ready: listing proxy pods:
client rate limiter Wait returned an error: context deadline exceeded

Every failing scenario fails at the cluster.go:163: ✓ preparing cluster done (311.0s) boundary — the harness's e2e-proxy DaemonSet never reports ready inside the prepare-cluster DAG's deadline.

Cross-PR pattern (same window): identical 236-failure / ~60% pattern on PR #8652 build 167387444, PR #8294 build 167387406, PR #8600 build 167387387, and earlier PR #8618 build 167378787. Same proxy-pod-readiness exhaustion + intermittent ResourceGroupBeingDeleted on shared kubenet-v5/networkisolated-v2 cluster pools.

Build-vs-test: test-infra (shared cluster fleet), NOT product, NOT PR-caused.
This PR's exposure check: ACL marketplace image bump (3.20260602.01). No path from a marketplace image-tag change to the e2e proxy DaemonSet's readiness behavior.
Confidence: HIGH that PR #8669 is not the cause.
Strongest alternative (less likely): ACL image bump breaking e2e-proxy DaemonSet — refuted by 4+ unrelated concurrent PRs hitting identical signature.

Recommended next action / owner: E2E infra / NodeSIG-dev — shared cluster fleet stabilization (proxy DaemonSet readiness + RG lifecycle). PR author: do NOT block merge intent on this; this is a draft PR — rerun once the shared cluster fleet recovers.

Posted by Clawpilot AgentBaker gate detective.