chore(deps): update acr-credential-provider (patch)

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
azure-acr-credential-provider		patch	1.36.1-ubuntu24.04u1 → 1.36.2-ubuntu24.04u1
azure-acr-credential-provider		patch	1.35.5-ubuntu24.04u1 → 1.35.6-ubuntu24.04u1
azure-acr-credential-provider	1.34.8-ubuntu24.04u1	patch	1.34.10-ubuntu24.04u1 → 1.34.11-ubuntu24.04u1
azure-acr-credential-provider	1.33.11-ubuntu24.04u1	patch	1.33.13-ubuntu24.04u1 → 1.33.14-ubuntu24.04u1
azure-acr-credential-provider		patch	1.36.1-ubuntu22.04u1 → 1.36.2-ubuntu22.04u1
azure-acr-credential-provider		patch	1.35.5-ubuntu22.04u1 → 1.35.6-ubuntu22.04u1
azure-acr-credential-provider	1.34.8-ubuntu22.04u1	patch	1.34.10-ubuntu22.04u1 → 1.34.11-ubuntu22.04u1
azure-acr-credential-provider	1.33.11-ubuntu22.04u1	patch	1.33.13-ubuntu22.04u1 → 1.33.14-ubuntu22.04u1
azure-acr-credential-provider		patch	1.36.1-ubuntu20.04u1 → 1.36.2-ubuntu20.04u1
azure-acr-credential-provider		patch	1.35.5-ubuntu20.04u1 → 1.35.6-ubuntu20.04u1
azure-acr-credential-provider	1.34.8-ubuntu20.04u1	patch	1.34.10-ubuntu20.04u1 → 1.34.11-ubuntu20.04u1
azure-acr-credential-provider	1.33.11-ubuntu20.04u1	patch	1.33.13-ubuntu20.04u1 → 1.33.14-ubuntu20.04u1

---

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

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=168642507
Failed job/stage/task: $(System.Collections.Hashtable.job)
First failing step/test: $(System.Collections.Hashtable.first)

RCA: E2E infra failure: NetworkIsolated scenario attempted VMSS create in MC RG MC_abe2e-westus3_abe2e-azure-networkisolated-v3-d6cc9_westus3, but ARM returned 409 ResourceGroupBeingDeleted because the RG is deprovisioning. Build VHD succeeded, so this is not caused by the ACR credential provider update.

Confidence: High for the primary signature. Corroborated by timeline/status, focused failed logs, associated changes, and the flakiness wiki before publishing.

Strongest alternative: the ACR credential provider update broke NetworkIsolated ACR behavior; less likely because the first failure is ARM VMSS create into a deleting resource group, before credential-provider behavior is tested.

Recommended owner/action: AgentBaker E2E test-infra: clean/recreate the stale NetworkIsolated MC RG and harden cluster acquisition around ResourceGroupBeingDeleted.

Wiki signature: $(System.Collections.Hashtable.sig) (source of truth)

[aks-node-assistant]

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=168775695
Failed job/stage/task: Run AgentBaker E2E
Summary: E2E failed with repeated kube.go:199 node readiness timeouts across unrelated scenarios (Test_Ubuntu2404_SecureTLSBootstrapping_BootstrapToken_Fallback, Test_Ubuntu2204_PMC_Install, Test_AzureLinuxV3_SecondaryNIC, etc.).
Likely cause/signature: known shared E2E cluster/fleet readiness flake, shared-cluster-fleet-outage.
Confidence: high; same node-ready timeout pattern hit unrelated PRs in the same window.
Strongest alternative: PR #8739's acr-credential-provider update broke provisioning; less likely because the failures are broad across OS/scenario families and match the existing infra signature.
Recommended next action/owner: E2E shared-cluster infra owners; continue repair item https://msazure.visualstudio.com/CloudNativeCompute/_workitems/edit/38373323.
Wiki: shared-cluster-fleet-outage — https://dev.azure.com/msazure/09706533-03bf-4b43-9a9b-b49c75429646/_wiki/wikis/ed4a85e9-1085-4151-a39b-2753523eba2b?pagePath=%2FAKS%2FSIGs%20and%20Teams%2FAKS%20Components%2FSIG%3A%20Node%20Lifecycle%2FAI%20Agent%20Knowledge%2FAgentBaker%20Gate%20PR%20Pipeline%20Flakiness

[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

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=168796814
Failed job/stage/task: Run AgentBaker E2E
Summary: E2E hit the known shared-cluster/fleet outage: �be2e-azure-overlay-dualstack-v6-4a24b was unexpectedly Deleting across SecondaryNIC dual-stack scenarios, and other validations showed NetworkUnavailable=True / Waiting for cloud routes. Concurrent CIS/SSH lane issues are separate.
Likely cause/signature: shared-cluster-fleet-outage.
Confidence: high.
Strongest alternative: PR #8739's acr-credential-provider dependency bump caused node/network readiness issues; less likely because the same shared cluster lifecycle/network-route signature appears across unrelated PRs.
Recommended next action/owner: E2E shared-cluster infra owners; continue repair item https://msazure.visualstudio.com/CloudNativeCompute/_workitems/edit/38373323.
Wiki: shared-cluster-fleet-outage — https://dev.azure.com/msazure/09706533-03bf-4b43-9a9b-b49c75429646/_wiki/wikis/ed4a85e9-1085-4151-a39b-2753523eba2b?pagePath=%2FAKS%2FSIGs%20and%20Teams%2FAKS%20Components%2FSIG%3A%20Node%20Lifecycle%2FAI%20Agent%20Knowledge%2FAgentBaker%20Gate%20PR%20Pipeline%20Flakiness

[Copilot]

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