-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CI VM for debian12 #10222
Add CI VM for debian12 #10222
Conversation
Ah wait I am confused actually the other PR have the same change isn't it? |
Hi @MrFreezeex If the kubespray needs to add a new OS, the OS's kubevirt image needs to be build and update to the https://quay.io/organization/kubespray manually :-) The PR is to build and image , and the image is still pushing. :-) |
Ohhhh ok I see thanks, for my curiosity I don't see any job on gitlab ci that would do that, so is it something that you invoke manually from your machine or? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @yankay
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MrFreezeex, mzaian, yankay The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I haven't been seen quay.io/kubespray/vm-debian-12 so far, I'm also curious about how it building and pushing :-) |
Hi @tu1h It's at https://quay.io/repository/kubespray/vm-debian-12?tab=tags&tag=latest |
Thanks @MrFreezeex @mzaian for the PR review :-) |
It shows CI still failed https://gitlab.com/kargo-ci/kubernetes-sigs-kubespray/-/jobs/4485281106 |
What type of PR is this?
/kind flake
What this PR does / why we need it:
To support debian12, add CI vm for the debian12 at: https://quay.io/kubespray/vm-debian-12
Support the #10221
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: