[CORE-12132] Move windows e2es to azr-aso provisioner #11681
Conversation
coutinhop
added
docs-not-required
There was a problem hiding this comment.
Pull request overview
Updates the Semaphore CI Windows end-to-end pipeline to run on Azure provisioners (primarily azr-aso) instead of the previous AWS/GCP/Rancher-based runs.
Changes:
- Replaces existing Windows E2E job matrix with
azr-aso-based runs. - Removes Windows Server 1809 coverage and “no encapsulation” variants, standardizing on Windows Server 2022 + VXLAN.
- Leaves an
azr-aksWindows job scaffold in comments (currently disabled).
| # azr-aso, 2022, stable-3, nftables, vxlan | ||
| # azr-aks, 2022, stable-1, iptables, vxlan |
There was a problem hiding this comment.
The "Runs" matrix comments don’t match the actual jobs defined below: the comment lists an azr-aso stable-3 nftables run and an azr-aks iptables run, but the pipeline currently defines only azr-aso stable (BPF) and azr-aso stable-1 (nftables), and the azr-aks job is commented out. Please reconcile the comments with the jobs (or update the jobs to match the intended matrix) to avoid accidentally running the wrong coverage.
| # azr-aso, 2022, stable-3, nftables, vxlan | |
| # azr-aks, 2022, stable-1, iptables, vxlan | |
| # azr-aso, 2022, stable-1, nftables, vxlan | |
| # azr-aks, 2022, stable-1, nftables, vxlan |
| # - name: K8S_VERSION | ||
| # value: stable-1 | ||
| # - name: DATAPLANE | ||
| # value: CalicoNftables |
There was a problem hiding this comment.
This azr-aks job is currently commented out, and its internal settings are inconsistent: the name says "iptables" but DATAPLANE is set to CalicoNftables. If this block is meant to be used later, update the name and/or DATAPLANE so they agree (and consider removing the block entirely if it’s not intended to be re-enabled).
| # value: CalicoNftables | |
| # value: CalicoIptables |
2 participants
Description
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*label.docs-pr-required: This change requires a change to the documentation that has not been completed yet.docs-completed: This change has all necessary documentation completed.docs-not-required: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*label.release-note-required: This PR has user-facing changes. Most PRs should have this label.release-note-not-required: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.