chore(deps): update oss/v2/azure/ip-masq-agent-v2 docker tag to v0.1.16-17

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
oss/v2/azure/ip-masq-agent-v2	v0.1.16-15	patch	v0.1.16-16 → v0.1.16-17

---

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: Never, 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.

[github-actions]

Posted 1 suggested fix(es) for previousLatestVersion below -- click a suggestion's "Add suggestion to batch" (or "Commit suggestion") button to apply it directly to this PR.

[Copilot]

Copilot review overview

🔵 Needs a closer look

The networking image’s upstream changes and AKS-RP version coordination could not be verified.

Review effort: Balanced
Findings: None

What changed in this PR

Updates the cached Linux VHD networking image for ip-masq-agent-v2.

Changes:

• Promotes v0.1.16-17 as latest.
• Retains v0.1.16-16 as the fallback version.

Package Update Analysis: ip-masq-agent-v2

Version change: v0.1.16-16 → v0.1.16-17 (patch/build-revision update)
OS variants affected: Ubuntu 20.04–26.04, Azure Linux 3, and Azure Container Linux variants on AMD64/ARM64
OS variants NOT updated: None among currently cached Linux variants; Windows is intentionally excluded.

Changes between v0.1.16-16 and v0.1.16-17

Change	Description	Risk
Unknown	Upstream changelog was unavailable for this version range.	🔴 High

The registry path and artifact naming remain unchanged. The new image size is not yet available; the prior image is approximately 24–27 MiB depending on architecture. AKS-RP version coordination could not be verified, so the component owner should confirm v0.1.16-15 is no longer required from newly built VHD caches.

Overall Risk: 🔴 High

Justification: This is a production networking component without an available upstream change summary or verified AKS-RP coordination.
Recommendation: Perform manual networking validation and obtain component-owner confirmation before merging.

File	Description
parts/​common/​components.json	Advances the cached multi-architecture image and fallback version.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

Windows Unit Test Results

  3 files   17 suites   1m 12s ⏱️
533 tests 533 ✅ 0 💤 0 ❌
536 runs  536 ✅ 0 💤 0 ❌

Results for commit 20ce358.

♻️ This comment has been updated with latest results.

[aks-node-assistant]

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=182262460
Failed job/stage/task: build / build2204fipsgen2containerd / Test, Scan, and Cleanup.

Detective summary: Test/Scan completed the VHD scan, then the CIS baseline comparison again found Ubuntu 22.04 FIPS rules 5.1.18 and 5.1.6 regressed from pass to fail. This is the existing repair-linked CIS baseline-drift signature.

Likely cause / signature: $cisSig.

Confidence: High for recurring baseline drift.

Recommended owner/action: VHD validation owners should work repair #39802117 to reconcile the CIS baseline or fix image content.

Strongest alternative: PR-specific ip-masq component changes caused the CIS diff; less likely because the same two CIS rules reproduced across unrelated PRs and manual branches.

Evidence: Timeline marks Test/Scan as succeededWithIssues; task log reports CIS regressions detected: 2 with 5.1.18|pass->fail and 5.1.6|pass->fail; existing wiki row and repair item track this recurring signature.

Wiki signature: $cisSig; repair #39802117

[github-actions]

Posted 1 suggested fix(es) for previousLatestVersion below -- click a suggestion's "Add suggestion to batch" (or "Commit suggestion") button to apply it directly to this PR.

[github-actions]

Best-effort recommendation from the previousLatestVersion check: the highest build found upstream for this release.

Suggested change

	"previousLatestVersion": "v0.1.16-16"
	"previousLatestVersion": "v0.1.15-25"

[github-actions]

previousLatestVersion needs a fix

One or more changed entries in parts/common/components.json have a previousLatestVersion problem: either it points at the same release as latestVersion (must reference a genuinely prior release), or it's a real prior release but not the newest build known upstream for that release. Where a recommendation was found, this check also posted it as an inline GitHub suggested-change review comment on the affected line below -- use its "Add suggestion to batch" / "Commit suggestion" button to apply the fix directly to this PR (or set a different value if you know a better one).

Entry	Issue	latestVersion	previousLatestVersion (current)	Suggested previousLatestVersion
root.ContainerImages[24].multiArchVersionsV2[0]	same release as latestVersion	v0.1.16-17	v0.1.16-16	v0.1.15-25

Suggestions are best-effort: the highest build this check found upstream for the relevant release. If a suggested value doesn't actually exist, a later CI step (schema/build validation) will catch it.

[github-actions]

Package	Line Rate	Health
github.com/Azure/agentbaker/aks-node-controller	72%	➖
github.com/Azure/agentbaker/aks-node-controller/common	100%	✔
github.com/Azure/agentbaker/aks-node-controller/helpers	71%	➖
github.com/Azure/agentbaker/aks-node-controller/parser	89%	✔
github.com/Azure/agentbaker/aks-node-controller/pkg/gpu	100%	✔
github.com/Azure/agentbaker/aks-node-controller/pkg/nodeconfigutils	67%	➖
github.com/Azure/agentbaker/aks-node-controller/utils	0%	❌
github.com/Azure/agentbaker/apiserver	25%	❌
github.com/Azure/agentbaker/cmd	0%	❌
github.com/Azure/agentbaker/cmd/starter	0%	❌
github.com/Azure/agentbaker/fuzz/api	0%	❌
github.com/Azure/agentbaker/hotfix/render-nodecustomdata	0%	❌
github.com/Azure/agentbaker/pkg/agent	76%	➖
github.com/Azure/agentbaker/pkg/agent/datamodel	76%	➖
github.com/Azure/agentbaker/pkg/agent/toggles	0%	❌
github.com/Azure/agentbaker/pkg/vhdbuilder/datamodel	88%	✔
Summary	74% (6316 / 8578)	➖

[github-actions]

Package	Line Rate	Health
shellspec spec	21%	❌
Summary	21% (3032 / 14138)	❌

[github-actions]

Package	Line Rate	Health
test	0%	❌
windows	21%	❌
staging_cse_windows Package 1	65%	➖
debug	0%	❌
provisioningscripts	2%	❌
parts_windows Package 1	76%	➖
Summary	37% (1598 / 6790)	❌

[aks-node-assistant]

AgentBaker Linux gate detective

Run: https://msazure.visualstudio.com/CloudNativeCompute/_build/results?buildId=182354509
Failed job/stage/task: build / build2204fipsgen2containerd / Test, Scan, and Cleanup.

Detective summary: Test/Scan completed the VHD scan, then the CIS baseline comparison again found Ubuntu 22.04 FIPS rules 5.1.18 and 5.1.6 regressed from pass to fail. This matches the existing repair-linked CIS baseline-drift signature rather than a new PR-local failure.

Likely cause / signature: vhd-ubuntu2204fips-cis-cron-rules-regression.

Confidence: High for recurring baseline drift.

Recommended owner/action: VHD validation owners should continue repair #39802117 to reconcile the CIS baseline or fix image content; no pipeline retry is recommended from this RCA.

Strongest alternative: PR-specific component change caused the scan diff; less likely because the same two CIS rules are repeating across unrelated PRs and the PR changes are not in the CIS scan path.

Evidence: Timeline marks Test/Scan as succeededWithIssues; task log reports CIS regressions detected: 2 with 5.1.18|pass->fail and 5.1.6|pass->fail; existing wiki row and repair #39802117 already track this recurring signature.

Wiki signature: $sigCis; repair #39802117