Fix: Use correct Windows Server 2022 template for vSphere provisioning - #83447
Fix: Use correct Windows Server 2022 template for vSphere provisioning#83447rrasouli wants to merge 1 commit into
Conversation
The clusterBot provisioning pipeline was using a stale template reference (windows-server-2022-template-qe-20241104) that no longer exists, causing all Windows node provisioning to fail. Update to use the correct ipv6-disabled template that is actively maintained in vSphere infrastructure. Fixes consistent Windows node provisioning failures on vSphere clusters.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe vSphere Windows machineset configuration now selects the IPv6-disabled Windows Server 2022 image template by default. ChangesWindows vSphere machine template
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized change updates the Windows Server 2022 provisioning template reference; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rrasouli The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@rrasouli: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
The clusterBot provisioning pipeline was using a stale template reference (windows-server-2022-template-qe-20241104) that no longer exists, causing all Windows node provisioning to fail. Update to use the correct ipv6-disabled template that is actively maintained in vSphere infrastructure.
Fixes consistent Windows node provisioning failures on vSphere clusters.
Summary by CodeRabbit