-
Notifications
You must be signed in to change notification settings - Fork 395
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 Ubuntu 22.04 LTS for Azure #961
Conversation
/hold |
caf69ad
to
b0f7233
Compare
/hold cancel I've finally done some local testing with this, by building a Ubuntu 22.04 managed image and provisioning CAPZ clusters. Seems to be working. |
@andyzhangx @CecileRobertMichon @jackfrancis please take a look. |
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.
/lgtm
/lgtm
This add three more VMs we build for CI. Do we have a plan to remove some at any point? |
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.
/lgtm
btw, are we also going to support Mariner 2.0 in this repo? thanks.
+1, let's remove 18.04? |
At one point we discussed publishing 18.04 images until Ubuntu stops publishing updates, which I think is April 2023. But I have no objection to stopping that earlier if we all agree. I plan to publish Ubuntu 22.04 images for the most recent k8s patch releases as soon as this merges, and then continue to publish 22.04 going forward. Also, the images we choose to publish are distinct from the tools in this repo. That is, we don't have to remove |
That would be excellent. I don't think anyone is working on this currently, though. |
Agreed, in addition we can run CI on a subset as well. |
I vote for keeping Ubuntu 18.04 as it's still being used. Since builds are being run in parallel it should not increase the ci time by too much. |
My concern is more $ and subscription quota, each CI job creates a VM for each image type. Right now we have:
and
So 20 VMs for each PR run, which is a lot. If we could make CI a subset of these or at least make some of them optional and not run by default that would help. Not saying we should remove support for 18.04 right away, just concerned about CI. |
I can remove (Could we do this for |
Yes I think so. I believe we stopped running dockershim tests (@jackfrancis to confirm) in capz. Especially now that 1.22 is the latest release which supports containerd in capz |
b0f7233
to
c291f20
Compare
related to #994 |
flatcar failed /retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx, jackfrancis, jsturtevant, mboersma 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 |
What this PR does / why we need it:
Adds Ubuntu 22.04 LTS build support to Azure.
Which issue(s) this PR fixes:
Refs #960
Additional context:
I've tested this and it builds successfully in our DevOps pipeline, but the resulting images need to be tested in a Kubernetes environment.