chore(config): bump opstool AKS to 1.34 toward fleet parity (AROSLSRE-1414)

[Rael Garcia (raelga)]

AROSLSRE-1414 (parent AROSLSRE-863)

What

Bump the opstool AKS kubernetesVersion in config/config-dev-ci.yaml from "1.33" to "1.34" — the next step toward fleet parity (1.35).

Why

opstool-usw3 is now on 1.33 (control plane and all three node pools at 1.33.12, node image 202606.19.0), while the rest of the fleet runs 1.35. AKS upgrades one minor at a time, so this PR advances the next hop 1.33 → 1.34; a follow-up will take it to 1.35.

Bumping kubernetesVersion drives the opstool-aks-pipeline (dev-infrastructure/scripts/upgrade-aks-cluster.sh → az aks upgrade) to upgrade the control plane and roll the node pools onto the target minor. az aks get-upgrades confirms 1.34.x is the only available upgrade target from 1.33.

Testing

No code paths change; this is a config version bump validated by the existing config schema (config/config-dev-ci.schema.json types kubernetesVersion as a string). cd config && make materialize produces no rendered-config changes (opstool config is not part of the rendered tree).

Post-deploy validation on opstool-usw3:

• az aks show ... --query kubernetesVersion → 1.34
• az aks nodepool list ... --query "[].currentOrchestratorVersion" → 1.34.x on all pools

Special notes for your reviewer

Scope is intentionally limited to opstool (dev-ci). The product svc/mgmt clusters are already on 1.35 and are not affected. The 1.33 hop merged in #5988 (pipeline fix so node pools roll, not just the control plane) and #5936 (the 1.33 config bump), and has been rolled out and verified.

PR Checklist

• PR is scoped to a single task (no mixed concerns)
• Title follows Conventional Commits format
• Summary explains the "Why" behind the change
• Linked to relevant ticket/issue
• Screenshots included (if graph/UI/metrics changes)
• Self-reviewed the diff
• CI/CD checks are passing (ignore Tide)
• Draft PR used for WIP (if applicable)
• Commit history is clean (rebased/squashed)
• Tricky code blocks are commented
• Specific reviewers tagged
• All comment threads resolved before merge

[Copilot]

Pull request overview

This PR advances the dev-ci opstool AKS cluster configuration toward fleet parity by bumping the configured Kubernetes minor version from 1.33 to 1.34. This aligns with the documented one-minor-at-a-time AKS upgrade path and should drive the existing opstool upgrade pipeline behavior without changing any code paths.

Changes:

• Bump clouds.*.opstool.aks.kubernetesVersion in config/config-dev-ci.yaml from "1.33" to "1.34".

[roi (roivaz)]

/lgtm
/approve

[Venkatesh S (venkateshsredhat)]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: raelga, roivaz, venkateshsredhat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• config/OWNERS [raelga,roivaz,venkateshsredhat]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Rael Garcia (raelga)]

e2e-parallel failed, retriggering as a flake — not caused by this PR.

Evidence:

• This PR changes only config/config-dev-ci.yaml (opstool kubernetesVersion 1.33→1.34), a dev-ci-only knob that e2e-parallel does not exercise.
• All 10 other required prow checks are green (verify, lint, test-unit, integration, images, config-change-detection, etc.).
• e2e-parallel is currently red across several unrelated PRs (feat: move and enable asynchronous CS create interaction for externalauths #6041, chore: route kernel (kmsg) logs to Kusto systemdLogs for node-freeze investigation #6040, do not merge: OCPBUGS-98213 Verification #6033) and green on others (feat: enable setting maxSurge and maxUnavailable per env #6038, backend: add a controller to auto-scale the Azure Monitor Workspace #6036) in the same window — an intermittent fleet-wide/infra flake, the same signature seen on the parent hop fix(dev-ci): upgrade opstool AKS node pools, not just control plane (AROSLSRE-1414) #5988.

/test e2e-parallel

[Rael Garcia (raelga)]

Retriggering e2e-parallel again — second failure is a different, unrelated flake (not PR-caused).

The build's only failing case was in the observability alert lane, not a functional e2e test:

[aro-hcp-observability] [svc] alert BackendAsyncOperationExternalAuthDeleteStuck does not fire
  -> alert fired 1 time(s); State: Resolved; 12:15:49Z -> 12:23:53Z (Sev3)
  on cluster ci01-j5847040-svc, externalauth delete async op

This is a transient backend async-operation alert on the e2e svc cluster that auto-resolved after ~8 min. This PR only changes config/config-dev-ci.yaml (opstool dev-ci k8s 1.33→1.34) and cannot influence the e2e svc-cluster alert lane. All 10 other required checks are green.

/test e2e-parallel