From Fedora Project Wiki
DRAFT
Fedora Kubernetes Ecosystem Roadmap 2022-2023
Definition
The Kubernetes ecosystem in Fedora is defined to encompass the CRI-O package, the CRI-Tools package and the Kubernetes package from the Fedora dnf repository. All three components are designed to be deployed with a synchronized major:minor version. If Kubernetes 1.24.3 is installed on one or more machines, then both CRI-O and CRI-Tools should also be installed at the same 1.24 version (if used). By definition, patch level versions can differ.
Current State in Fedora
| Package | Role | Release RPMs | Modular RPMs | Dependencies Between These Packages |
|---|---|---|---|---|
| CRI-O | Container runtime for Kubernetes | No | Yes | None. One of several container runtime options for kubernetes |
| CRI-Tools | provides crictl and other cli tools | Partial | Yes; bundled with CRI-O | Required by kubeadm |
| Kubernetes | Container orchestration | Yes | No | CRI-O is optional, CRI-Tools required by kubeadm |
Roadmap and Goals
The following list contains goals and deliverables for the 2022-2023 timeframe. The list is not in any special order.
- Create and maintain release rpms at target version(s) for each Fedora release for all packages.
- Create and maintain modular rpms at target versions-Fedora release combinations for all packages.
- Formalize appropriate coordination between package maintainers. Coordination needed to synchronize on versions
- Separate CRI-Tools into it's own module. Currently bundled with CRI-O module but this is mostly for convenience.
Questions
- Is a coordinated communication plan desirable and/or beneficial? A plan might include a mailing list, matrix group, Fedora doc page especially on modular install and update of these components on Fedora.
- These are all go language based software. What role can or should the go-sig have?
- Who will be the CRI-Tools maintainers?