Update Kubernetes tasks to use latest dependencies

[ivanduplenskikh]

Predecessor

#21883 - the PR was closed due and all changes were included here since BuildConfigGen starts every PR check

Related WI: AB#2361733

Summary of changes

• Updated Kubernetes-related task dependencies to current shared packages and aligned generated artifacts.
• Bumped task versions for Kubernetes tasks and related Azure tasks impacted by regeneration.
• Regenerated lockfiles and _generated Node24/versionmap outputs to match the new dependency and version state.

Motivation / context

• Keeps Kubernetes task dependency stack current, reduces drift with shared task libraries, and keeps generated build-config outputs consistent with task metadata.

File-grouped change overview

• Build tooling (BuildConfigGen)
  • Updated baseline azure-pipelines-task-lib to ^5.2.6.
  • Added rewrite for azure-pipelines-tasks-kubernetes-common to alias npm:azure-pipelines-tasks-k8s-common@^2.270.1 when dependency exists.
• Task manifests (Tasks/**/package.json)
  • Kubernetes tasks updated: azure-pipelines-task-lib (^5.2.6), azure-pipelines-tasks-azure-arm-rest (^3.270.0 where applicable), azure-pipelines-tasks-utility-common (^3.270.0 where applicable), and Kubernetes common aliasing.
• Task metadata (Tasks/**/task.json, task.loc.json)
  • Version bumps applied (many tasks moved to 271.0; AzureKeyVaultV2 patch incremented).
• Generated artifacts (_generated/**, lockfiles)
  • Updated _generated/*_Node24 task/package files and _generated/*.versionmap.txt to new default/Node24 mappings.

Breaking changes

• None expected for task consumers; this is dependency/version maintenance plus generated metadata alignment.

Testing notes

• No additional local test logs attached in this PR body update.
• Suggested validation: build + L0 for KubernetesV1, KubernetesManifestV1, HelmInstallerV1, KubectlInstallerV0, AzureFunctionOnKubernetesV1.

Deployment notes

• No special deployment or migration steps beyond standard task publishing flow.

Links to related issues or tickets

• Existing work item link: AB#2361742

---

Context

WI: AB#2361742

• Updated azure-pipelines-task-lib from ^5.2.4 to ^5.2.6
• Updated azure-pipelines-tasks-azure-arm-rest from 3.267.1 to ^3.270.0
• Updated azure-pipelines-tasks-kubernetes-common to npm:azure-pipelines-tasks-k8s-common@^2.270.1
• Updated azure-pipelines-tasks-utility-common from 3.267.0 to ^3.270.0
• Bumped task version from 1.269.1 to 1.271.0 in task.json and task.loc.json
• Updated dependencies in package-lock.json for Kubernetes tasks

---

Task Name

Name of the updated or newly created pipeline task.

---

Description

Summarize the changes made in this PR clearly and concisely.

---

Risk Assessment (Low / Medium / High)

Assess the level of risk and provide reasoning (e.g., scope, impact, backward compatibility).

---

Change Behind Feature Flag (Yes / No)

Can this change be behine feature flag, if not why?

---

Tech Design / Approach

• Design has been written and reviewed.
• Any architectural decisions, trade-offs, and alternatives are captured.

---

Documentation Changes Required (Yes/No)

Indicate whether related documentation needs to be updated.

• User guides, API specs, system diagrams, or runbooks are updated.

---

Unit Tests Added or Updated (Yes / No)

Indicate whether unit tests were added or modified to reflect these changes.

---

Additional Testing Performed

List all other tests performed (manual or automated, including integration, regression, scenario tests, etc.).

---

Logging Added/Updated (Yes/No)

• Appropriate log statements are added with meaningful messages.
• Logging does not expose sensitive data.
• Log levels are used correctly (e.g., info, warn, error).

---

Telemetry Added/Updated (Yes/No)

• Custom telemetry (e.g., counters, timers, error tracking) is added as needed.
• Events are tagged with proper metadata for filtering and analysis.
• Telemetry is validated in staging or test environments.

---

Rollback Scenario and Process (Yes/No)

• Rollback plan is documented.

---

Dependency Impact Assessed and Regression Tested (Yes/No)

• All impacted internal modules, APIs, services, and third-party libraries are analyzed.
• Results are reviewed and confirmed to not break existing functionality.

---

Checklist

• Related issue linked (if applicable)
• Task version was bumped — see versioning guide
• Verified the task behaves as expected

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[ivanduplenskikh]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).