Fedora Kubernetes Packages

Kubernetes rpms for Fedora.

Fedora and Kubernetes Release Matrix

Kubernetes releases are tracked upstream at Upstream is the canonical source for Kubernetes lifecycle plans and status. Information in the table and paragraphs below may be dated. The golang version in the table below is the major:minor version used by upstream to build and test the release. The specific golang patch release used by Kubernetes can and will change.

Kubernetes Version Target Fedora Release Kubernetes Planned End of Life Golang Built With
1.30 TBD TBD 1.22
1.29 F40 2025.02.28 1.21
1.28 F40 COPR 2024.10.28 1.20 1.21
1.27 F39 2024.06.28 1.20 1.21
1.26 EOL F38 2024.02.24 1.19 1.20 1.21
1.25 EOL F37 COPR F37 EOL 2023.10.27 1.19 1.20
1.24 EOL F36 EOL 2023.07.28 1.18 1.19 1.20
1.23 EOL COPR EOL 2023.02.28 1.17 1.19
1.22 EOL F35 EOL 2022.10.28 1.16

Kubernetes 1.30 is available at This is an alpha level release. These rpms have the revised package layout. RPMS available for rawhide (F40) only.

Kubernetes 1.29 is available at They have a revised package layout.

Kubernetes 1.28 is available at

Kubernetes 1.27 is available in COPR at:

Kubernetes Package Workflow

1 Feb 2024. The workflow to revise the spec file now uses the script. This script uses a configuration file (newrelease.conf) and a template spec file to generate a revised spec file for use in the standard Fedora build processes. Edits made directly to the spec file will be over-written during the next update cycle.

Important: the template uses the revised package structure. Do not use this workflow for F39 or F38 branches at this time.

Generate a configuration file, if none present

  1. Run -c

Upstream has a new minor or patch release

  1. Edit the newrelease.conf file with the revised patch number.

  2. Run -y

  3. Follow normal Fedora build and release process.

Other modifications to the spec file to fix errors or add features

  1. Edit the template (initially ./template/kubernetes-template.spec but set in configuration file)

  2. Run -y

  3. Follow normal Fedora build and release process.