-
Notifications
You must be signed in to change notification settings - Fork 501
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
Integrate CRI-O into krel obs
#3214
Comments
+1 from me. In my ideal we wouldn't have to release before kubernetes but that's not a hard blocker for me |
I think we can also release afterwards if we do not make the kubelet dependent on CRI-O, which we would probably not do in any case. |
Successfully pushed v1.28.1 via:
https://build.opensuse.org/package/show/isv:kubernetes:core:shared:build/cri-o |
Another run containing #3268 and #3269:
Logs: https://console.cloud.google.com/cloud-build/builds/e3b3d258-3ed3-4748-832a-b1cf38590867?project=648026197307 Test of the
|
I'll help with a new home project for the package, let's sync about this tomorrow. |
I think this can be considered done now, we just have to publish a bunch of releases and slight upstream fixes like cri-o/cri-o#7312 |
The packaging of "cri-o" probably needs something similar to the packaging of "containerd.io" :
To help sort out the conflicts with the regular system packages, that also installs the same binaries.
|
Yeah I'm going with the runtime dependencies here: #3282 |
Hard to win that game, since it will then get whatever versions of conmon and crun the system has...
|
It will ensure somehow compatibility with the podman package, not sure. We can either break this or that 🤔 |
The CRI-O project wants to simplify it's packaging process and integrate it tighter into the Kubernetes infrastructure. CRI-O already uses OBS for the various supported release branches, where everything is built from source.
Goal for 1.29 is to integrate CRI-O into k/release by using the same pattern as other tools like cri-tools use together with
krel obs
.Useful information
CRI-O already produces static binary bundles for amd64, arm64 and ppc64le
(s390x support is blocked by
pkgsCross.s390.stdenv
broken by #238154 NixOS/nixpkgs#243614)The bundle contains all runtime dependencies which are required (and optional) to run CRI-O, means we can omit some of its content (like the cni-plugins, make that a requirement in the spec).
We probably need to change the CRI-O release cycle to release ahead of Kubernetes like we did in:
Release ahead of Kubernetes kubernetes-sigs/cri-tools#1213 (cc @haircommander)
The text was updated successfully, but these errors were encountered: