Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

ci: plan for when the windows-2022 runner is retired

Aperta
  • Qualcosa non va?
#1,467 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
30/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, github-actions, kubernetes
Ambito
ci-cd, devops

Direzione di ricerca

Start from the e2e test on windows job in the GitHub Actions workflow files, where #1464 pinned windows-2022, and from the k3s setup that uses knicknic/temp-kubernetes-ci. Check whether DISM /Online /Add-Capability /CapabilityName:WMIC~~~~ works on a windows-2025 runner and how long it takes. Done means a recorded comparison of the three options, with one of them tested on a fork's CI run.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What would you like to be added?

A plan to move the e2e test on windows job off windows-2022 before GitHub retires that runner image.

#1464 pinned the job to windows-2022 because windows-latest (Windows Server 2025) no longer ships wmic, and the kubelet in the k3s from knicknic/temp-kubernetes-ci fails to start without it:

exec: "wmic": executable file not found in %PATH%

Options, roughly from smallest to largest:

  1. Stay on windows-2025 and add WMIC back before k3s starts. It is still available as a Windows optional feature: DISM /Online /Add-Capability /CapabilityName:WMIC~~~~. This needs a check that the capability can be installed on the hosted runner, and how long it takes.
  2. Replace knicknic/temp-kubernetes-ci with a cluster setup that does not need wmic, for example kind or k3d with Docker on Windows, if that works on hosted Windows runners.
  3. Run the Windows job against a cluster started on a Linux job, so Windows only runs the kusion binary.
Why is this needed?

GitHub has not announced a retirement date for windows-2022 yet. Under its runner image policy, the oldest Windows image is deprecated once a newer one is GA, with an announcement and brownouts before removal. When that happens, the Windows nightly will go red again with the same error as #1237.

Suggested by @elliotxx in the review of #1464. I'm happy to try option 1 first on my fork's CI and report back.

Lingua principale
Go
Stelle
1.3k
Fork
111
Merge medio
2g 12h
PR unite (30g)
2

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di KusionStack/kusion

Tutte le issue di KusionStack/kusion

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.