Learn more about these different git repos.
Other Git URLs
Retire the cri-o module and go back to publishing the following RPMs in a non-modular way: - cri-o - cri-tools
Please also make myself, @lorbus an admin of the both RPM dist-git repos.
cc @haircommander
See also: - https://pagure.io/fedora-infrastructure/issue/11351 - https://github.com/cri-o/cri-o/issues/6986
ASAP
-
cri-o not installable in Fedora 39+
Metadata Update from @phsmoura: - Issue tagged with: medium-gain, medium-trouble, ops
Metadata Update from @jnsamyak: - Issue assigned to jnsamyak
This seems to be done! I'll take a look into the retirement for the modules
PR is up on fedora-module-defaults for the same[1]
[1] https://pagure.io/releng/fedora-module-defaults/pull-request/246
Finally got around to investigate the absence of the 1.28 module, sorry for being late to the party.
Do we have any plan on how to handle the different release cycles?
Kubernetes has 3 minor releases per year, since cri-o keeps in sync with Kubernetes minor versions, this will result in-release upgrades for cri-o. It'll also result in potentially skipping a version when upgrading from e.g. Fedora 38 to 39 later down the line. While this could work for cri-o, this will cause issues with Kubernetes.
I guess for now I'll have to maintain an own crio build in copr instead of using the module branching.
Hello @sheogorath!
Is there anything you want releng to help with, please let us know! Otherwise, the retirement cri-o module is done from the fedora-module-defaults and is applied to all fedoras! I hope @lorbus might be able to help better but not sure :P
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
I'm still weighing what to do here.
OKD is likely moving towards pulling official upstream builds from pkgs.k8s.io (see https://kubernetes.io/blog/2023/10/10/cri-o-community-package-infrastructure/).
I'll try to set up some degree of packit.dev automation. Since there are roughly two k8s/cri-o releases in each Fedora cycle, the packages will likely be upgraded to next minor once per cycle.
That said, maintenance of the cri-o rpm is not very high on my prio list, so new co-maintainers are welcome.
Login to comment on this ticket.