-
Notifications
You must be signed in to change notification settings - Fork 71
Release: Update payloads for v0.16.0 #539
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
Release: Update payloads for v0.16.0 #539
Conversation
fidencio
left a comment
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, thanks @niteeshkd!
|
Ubuntu 22.04 test is failing. Looks like we're low on disk space. Not sure what the root cause is. cc @wainersm |
08a18ac to
1726049
Compare
Those runner usually have ~14GB free for utilization, which is rather low, mainly when we take into consideration the size of the payloads we have (due the recent switch to zst, on the Kata Containers side). With this said, let's take the approach already taken by peer-pods (and thanks Steve for the tip :-)), and free as much space as possible before running our tests. Signed-off-by: Fabiano Fidêncio <ffidenciodeo@nvidia.com>
Update the enclave-cc runtime payloads to point to the v0.11.0 release of enclave-cc and update the pre-reqs payload. Signed-off-by: Niteesh Dubey <niteesh@us.ibm.com>
Update Kata payloads to 3.21.0 and bump the pre-reqs payload for default, peer-pods and s390x ccruntimes Signed-off-by: Niteesh Dubey <niteesh@us.ibm.com>
Update operator version from v0.15.0 to v0.16.0. Signed-off-by: Niteesh Dubey <niteesh@us.ibm.com>
1726049 to
50d6426
Compare
Root cause is probably the Kata Containers payload increasing in size, due to our switch to Zstd. |
|
|
Are you suggesting to bump the nydus snapshotter version? It'd require a bump on the pre-req daemonset, and I don't think that scenario (the update) was tested before? |
|
Amazing, as the change I made is on the action itself, and it's a pull_request_targetm, we need to run the tests from an internal branch, which I just triggered. |
The version bump is on our release checklist. We've forgotten do it a few times so take my comment as a reminder. @niteeshkd did something similar in #532. |
It was done previously to sync with the kata-containers versions that has been tested. This is 0.15.2 still, so I don't think this is applicable? |
Then it makes sense to keep the req payload as it is. |
|
https://github.com/confidential-containers/operator/actions/runs/18000995615/job/51222679357 -- this is the run manually triggered with all the tests passing. I had to re-run the SEV-SNP one, but it passed on the second run. |
stevenhorsman
left a comment
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. Thanks @niteeshkd & @fidencio!
|
This PR requires someone with admin powers to merge (which I have, but I'd like someone else with admin powers to do so, so we share the responsibility ;-)). |
fitzthum
left a comment
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
let's keep a close eye on the post-merge jobs
c43f953
into
confidential-containers:main
PR for step#5 of checklist for v0.16.0