Buckaroogeek (talk | contribs) |
Buckaroogeek (talk | contribs) (Enable multiple Kubernetes versions for each Fedora release) |
||
| Line 6: | Line 6: | ||
== Summary == | == Summary == | ||
Provide all maintained Kubernetes releases in Fedora as multiple, versioned packages. Current practice is a separate release | Provide all maintained Kubernetes releases in Fedora as multiple, versioned packages. Current practice is a separate Kubernetes release matched with each Fedora release. | ||
This proposal is independent from https://fedoraproject.org/wiki/Changes/RestructureKubernetesPackages. | This proposal is independent from https://fedoraproject.org/wiki/Changes/RestructureKubernetesPackages. | ||
| Line 41: | Line 41: | ||
== Detailed Description == | == Detailed Description == | ||
The Kubernetes project maintains 3 concurrent versions. Each version has a defined life-cycle of approximately 1 year (https://https://kubernetes.io/releases/ for details and current versions). In this proposal a release is a major:minor version combination such as 1.28 or 1.27 and ignores any patch updates (e.g. 1.28.1 or 1.28.2 - this all are part of the same 1.28 release). | The Kubernetes project maintains 3 concurrent versions with a new release every 4 months. Each version has a defined life-cycle of approximately 1 year (https://https://kubernetes.io/releases/ for details and current versions). In this proposal a release is a major:minor version combination such as 1.28 or 1.27 and ignores any patch updates (e.g. 1.28.1 or 1.28.2 - this all are part of the same 1.28 release). | ||
We currently match one | We currently match one version of Kubernetes with each Fedora release. See https://src.fedoraproject.org/rpms/kubernetes for the list of Kubernetes releases by Fedora release. Due to the differing release cadences between Fedora and Kubernetes this means that a new release of Fedora may not have the most current release of Kubernetes. And, given that the Kubernetes cluster upgrade process does not permit skipping major:minor releases, not providing a Kubernetes release in Fedora so that the most current Kubernetes release is available when a Fedora release goes into production becomes a barrier to using Fedora as a host OS for Kubernetes. | ||
We propose to create packages for all current Kubernetes releases for each Fedora release starting with Fedora 40. The package name would follow the Fedora naming convention standard for multiple package versions of "kubernetes[major].[minor]". Using the kubernetes- | We propose to create packages for all current Kubernetes releases for each Fedora release starting with Fedora 40. The package name would follow the Fedora naming convention standard for multiple package versions of "kubernetes[major].[minor]". Using the kubernetes-client rpm as an example, instead of kubernetes-client-1.29.2-1.fc40 Fedora would offer kubernetes1.29-client-1.29.2-1.fc40, kubernetes1.28-node-1.28.5-1.fc40, and kubernetes1.27-node-1.27.8-1.fc40. The exact list of Kubernetes versions available will depend on what is supported upstream. | ||
We also propose that there not be any default version of Kubernetes for a given Fedora release. | We also propose that there not be any default version of Kubernetes for a given Fedora release. Fedora would not provide a kubernetes-client-1.29.2-1.fc40 package available. Default versions coupled to a given Fedora release can result in unplanned version updates to the installed Kubernetes version (i.e. v1.28 to v1.29) which can adversely affect a cluster. | ||
It is also important to note that each Kubernetes release is built with a specific version of the Go language. The version of Go available in a Fedora release will potentially be a constraint on which version of Kubernetes can be provided for an older Fedora release. | |||
We will also maintain a Kubernetes page on Fedora Quick Docs with information about the change and how to install Kubernetes using Fedora provided packages. | We will also maintain a Kubernetes page on Fedora Quick Docs with information about the change and how to install Kubernetes using Fedora provided packages. | ||
| Line 58: | Line 58: | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Fedora becomes a first class platform for Kubernetes using packages from Fedora repositories. That is, all current, maintained releases of Kubernetes are available in the main Fedora repositories. This allows Fedora as a host OS for a Kubernetes cluster to be maintained and upgraded independently of the Kubernetes release used by the cluster. This also allows the cluster to be upgraded independently of the Fedora release using Fedora provided packages. | Fedora becomes a first class platform for Kubernetes using packages from Fedora repositories. That is, all current, maintained releases of Kubernetes are available in the main Fedora repositories, subject to the Go language constraint. This allows Fedora, as a host OS for a Kubernetes cluster, to be maintained and upgraded independently of the Kubernetes release used by the cluster. This also allows the cluster to be upgraded independently of the Fedora release using Fedora provided packages. | ||
This also means that a Kubernetes cluster administrator using Fedora as their workstation can install and use or retain the appropriate Kubernetes command line client, kubectl, that matches the release of the cluster. Updating to a new Fedora release will not inadvertently install a command line client that is not compatible with the release version of the cluster(s) managed by the user. | This also means that a Kubernetes cluster administrator using Fedora as their workstation can install and use or retain the appropriate Kubernetes command line client, kubectl, that matches the release of the cluster. Updating to a new Fedora release will not inadvertently install a command line client that is not compatible with the release version of the cluster(s) managed by the user. | ||
<!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | <!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | ||
| Line 96: | Line 95: | ||
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Cri-o releases are version matched with Kubernetes release at the major:minor level. Cri-o currently uses modularity to provide multiple versions and | Cri-o releases are version matched with Kubernetes release at the major:minor level. Cri-o currently uses modularity in Fedora 38 and older to provide multiple versions. The cri-o package maintainer will adopt a similar approach to packaging and release in Fedora. | ||
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 111: | Line 110: | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
This change will require documentation in | This change will require documentation in on-line Fedora documentation such as the dedicated Quick Docs page and posts to various forums and mailing lists to raise awareness. Upgrading to Fedora 40 on a machine with Fedora 39 or Fedora 38 would require a manual step by the user to select the appropriate versioned Kubernetes package. | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== How To Test == | == How To Test == | ||
1. Install a versioned Kubernetes package on a fresh instance of Fedora and create a functioning test cluster. | |||
2. On a cluster node, replace a non-versioned Kubernetes package with a versioned package and rejoin cluster. There should not be any errors. | |||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | ||
| Line 134: | Line 137: | ||
== User Experience == | == User Experience == | ||
The user experience should remain unchanged except for the need to select a specific version of Kubernetes. | |||
<!-- If this change proposal is noticeable by users, how will their experiences change as a result? | <!-- If this change proposal is noticeable by users, how will their experiences change as a result? | ||
| Line 162: | Line 168: | ||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this change, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
Fedora Quick Docs: https://docs.fedoraproject.org/en-US/quick-docs/using-kubernetes/ | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Revision as of 21:36, 14 December 2023
Multiple Versioned Kubernetes Packages
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
Provide all maintained Kubernetes releases in Fedora as multiple, versioned packages. Current practice is a separate Kubernetes release matched with each Fedora release.
This proposal is independent from https://fedoraproject.org/wiki/Changes/RestructureKubernetesPackages.
Owner
- Name: Brad Smith
- Email: bradley.g.smith@gmail.com
Current status
- Targeted release: Fedora Linux 40
- Last updated: 2023-12-14
- [<will be assigned by the Wrangler> devel 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
The Kubernetes project maintains 3 concurrent versions with a new release every 4 months. Each version has a defined life-cycle of approximately 1 year (https://https://kubernetes.io/releases/ for details and current versions). In this proposal a release is a major:minor version combination such as 1.28 or 1.27 and ignores any patch updates (e.g. 1.28.1 or 1.28.2 - this all are part of the same 1.28 release).
We currently match one version of Kubernetes with each Fedora release. See https://src.fedoraproject.org/rpms/kubernetes for the list of Kubernetes releases by Fedora release. Due to the differing release cadences between Fedora and Kubernetes this means that a new release of Fedora may not have the most current release of Kubernetes. And, given that the Kubernetes cluster upgrade process does not permit skipping major:minor releases, not providing a Kubernetes release in Fedora so that the most current Kubernetes release is available when a Fedora release goes into production becomes a barrier to using Fedora as a host OS for Kubernetes.
We propose to create packages for all current Kubernetes releases for each Fedora release starting with Fedora 40. The package name would follow the Fedora naming convention standard for multiple package versions of "kubernetes[major].[minor]". Using the kubernetes-client rpm as an example, instead of kubernetes-client-1.29.2-1.fc40 Fedora would offer kubernetes1.29-client-1.29.2-1.fc40, kubernetes1.28-node-1.28.5-1.fc40, and kubernetes1.27-node-1.27.8-1.fc40. The exact list of Kubernetes versions available will depend on what is supported upstream.
We also propose that there not be any default version of Kubernetes for a given Fedora release. Fedora would not provide a kubernetes-client-1.29.2-1.fc40 package available. Default versions coupled to a given Fedora release can result in unplanned version updates to the installed Kubernetes version (i.e. v1.28 to v1.29) which can adversely affect a cluster.
It is also important to note that each Kubernetes release is built with a specific version of the Go language. The version of Go available in a Fedora release will potentially be a constraint on which version of Kubernetes can be provided for an older Fedora release.
We will also maintain a Kubernetes page on Fedora Quick Docs with information about the change and how to install Kubernetes using Fedora provided packages.
Feedback
To be provided.
Benefit to Fedora
Fedora becomes a first class platform for Kubernetes using packages from Fedora repositories. That is, all current, maintained releases of Kubernetes are available in the main Fedora repositories, subject to the Go language constraint. This allows Fedora, as a host OS for a Kubernetes cluster, to be maintained and upgraded independently of the Kubernetes release used by the cluster. This also allows the cluster to be upgraded independently of the Fedora release using Fedora provided packages.
This also means that a Kubernetes cluster administrator using Fedora as their workstation can install and use or retain the appropriate Kubernetes command line client, kubectl, that matches the release of the cluster. Updating to a new Fedora release will not inadvertently install a command line client that is not compatible with the release version of the cluster(s) managed by the user.
Scope
- Proposal owners:
With each new release of Kubernetes, package owners would request a new repository on src.fedoraproject.org from engineering similar to what the nodejs team now does for the parallel-installable versions of nodejs. Documentation would be refreshed to inform users of the new version and what specific Fedora releases the new version of Kubernetes would be available on.
- Other developers:
Cri-o releases are version matched with Kubernetes release at the major:minor level. Cri-o currently uses modularity in Fedora 38 and older to provide multiple versions. The cri-o package maintainer will adopt a similar approach to packaging and release in Fedora.
- Release engineering: #Releng issue number
Release engineering would need to create the new dist-git repository for each new Kubernetes release.
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Community Initiatives:
Upgrade/compatibility impact
This change will require documentation in on-line Fedora documentation such as the dedicated Quick Docs page and posts to various forums and mailing lists to raise awareness. Upgrading to Fedora 40 on a machine with Fedora 39 or Fedora 38 would require a manual step by the user to select the appropriate versioned Kubernetes package.
How To Test
1. Install a versioned Kubernetes package on a fresh instance of Fedora and create a functioning test cluster. 2. On a cluster node, replace a non-versioned Kubernetes package with a versioned package and rejoin cluster. There should not be any errors.
User Experience
The user experience should remain unchanged except for the need to select a specific version of Kubernetes.
Dependencies
No direct dependencies. If cri-o is installed and used as the container runtime then cri-o and kubernetes should have the same major:minor version.
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
Fedora Quick Docs: https://docs.fedoraproject.org/en-US/quick-docs/using-kubernetes/
N/A (not a System Wide Change)