Changes/VersionedCRI-OandCRI-ToolsPackages

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

Guidance
For details on how to fill out this form, see the documentation.

Report issues
To report an issue with this template, file an issue in the pgm_docs repo.

Multiple Versioned CRI-O and CRI-Tools Packages

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Cri-o and cri-tools versions are intended to match the version of Kubernetes that they are deployed with. FESCo recently approved multiple, version packages for Kubernetes (https://fedoraproject.org/wiki/Changes/VersionedKubernetesPackages). This Change Request, if approved, will allow Fedora to also provide correct versions of cri-o and cri-tools for Kubernetes administrators that use Fedora as the base machine OS.

Owner

• Name: Peter Hunt
• Email: pehunt@redhat.com

• Name: Brad Smith
• Email: bradley.g.smith@gmail.com

Current status

• Targeted release: Fedora Linux 41
• Last updated: 2024-05-01
• [Announced]
• [<will be assigned by the Wrangler> Discussion thread]
• FESCo issue: <will be assigned by the Wrangler>
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Both cri-o (https://src.fedoraproject.org/rpms/cri-o, upstream: https://github.com/cri-o/cri-o) and cri-tools (https://src.fedoraproject.org/rpms/cri-tools, upstream: https://github.com/kubernetes-sigs/cri-tools) are designed to version match the version of Kubernetes they are deployed with. Version matching is a guarantee to Kubernetes administrators that these components use the same API version of the target Kubernetes installation.

Starting in Fedora 41, users will be able to install any supported version of Kubernetes (typically 3 concurrent, supported versions) using, for example, "dnf install kubernetes1.30". This Change, if approved would allow the user to also install cri-o and/or cri-tools with the same version, i.e. "dnf install cri-o1.30 kubernetes1.30".

Cri-o is a well-regarded implementation of the container runtime interface (CRI). Each Kubernetes cluster requires a CRI implementation to function. Alternatives include containerd or Docker Engine among others.

Cri-tools contains the crictl command line interface tool that provides a CLI for CRI-compatible container runtimes. This allows the CRI runtime developers to debug their runtime without needing to set up Kubernetes components.

Feedback

TBD

Scope

• Proposal owners:

• Other developers:

• Release engineering: #Releng issue number

• Policies and guidelines: N/A (not needed for this Change)

• Trademark approval: N/A (not needed for this Change)

• Alignment with the Fedora Strategy:

Early Testing (Optional)

Do you require 'QA Blueprint' support? Y/N

Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)