-
Notifications
You must be signed in to change notification settings - Fork 123
[DO NOT MERGE] CI: bump k8s to v1.34 #2657
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
base: main
Are you sure you want to change the base?
Conversation
c84c5bf to
3bb1aba
Compare
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
|
@stevenhorsman @bpradipt I did this PR just to test one thing for Fabiano but, hey, it worked out. Maybe we should update k8s version used in our tests? At least the version in libvirt and aws. I can try to bump docker too. |
Yeah, I'm all for this |
|
Hi @BbolroC , This PR updates the worker image to ubuntu 2404 of kcli's created cluster. kcli needs to cache the new image on the runner, and it's getting permission denied in the s390x node: Could you change the permission? or maybe safer, download the image manually with |
@wainersm here is an ACL output: $ getfacl /var/lib/libvirt/images
getfacl: Removing leading '/' from absolute path names
# file: var/lib/libvirt/images
# owner: root
# group: root
user::rwx
user:ansible:rwx #effective:--x
group::--x
mask::--x
other::--xSo the Now the CI job should pass, I believe. 😉 |
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
It worked out @BbolroC ! thank you so much! |
|
Removed the tags that triggers for aws and libvirt because I'm going to push a commit to update docker (let's only tests on that provider now). I had to build a new kindnode image with cri-o, as kindest/node is containerd. Used the guide in https://github.com/cri-o/cri-o/blob/main/tutorials/crio-in-kind.md#build-node-image . Pushed the image to my area in quay.io; if tests pass then I will push it to confidential-container's repository. |
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
|
I've seen some cni related errors in the logs, let's try the newest calico |
|
The error in docker is about the new image I created for cri-o. I followed https://github.com/cri-o/cri-o/blob/main/tutorials/crio-in-kind.md#build-node-image , except that i could not build the base kind image so I leveraged CoCo operator pre-install pod fails at very last instruction, when it tries to If I use kindest/node:v1.34.0 then coco operator installs correctly. It is indeed something wrong with my image. |
I'd like to test peer pods with K8S 1.34.1 + CRI-O but on my laptop kcli has been hit by "Too many requests" errors from github. Let me try it on CI....