|
|
||
|---|---|---|
| template | ||
| .gitignore | ||
| 10-kubeadm.conf | ||
| build-with-debug-info.patch | ||
| changelog | ||
| environ-apiserver | ||
| environ-config | ||
| environ-controller-manager | ||
| environ-kubelet | ||
| environ-kubelet.kubeconfig | ||
| environ-proxy | ||
| environ-scheduler | ||
| go-vendor-tools.toml | ||
| kube-apiserver.service | ||
| kube-controller-manager.service | ||
| kube-proxy.service | ||
| kube-scheduler.service | ||
| kubelet.env | ||
| kubelet.service | ||
| kubernetes-accounting.conf | ||
| kubernetes.conf | ||
| kubernetes.sysusers | ||
| kubernetes1.32.spec | ||
| MAINTAINERS-CHANGELOG.md | ||
| newrelease | ||
| README.md | ||
| sources | ||
kubernetes1.32
Kubernetes v1.32 rpms for Fedora.
Kubernetes releases are tracked upstream at https://kubernetes.io/releases/. Upstream is the canonical source for Kubernetes lifecycle plans and status.
Kubernetes Package Workflow
The workflow to revise the spec file uses the newrelease 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.
Generate a configuration file, if none present
-
Run
newrelease -c
Upstream has a new minor or patch release
-
Edit the newrelease.conf file with the revised patch number.
-
Run
newrelease -y -
Follow normal Fedora build and release process.
Other modifications to the spec file to fix errors or add features
-
Edit the template (initially
./template/kubernetes-template.specbut set in configuration file) -
Run
newrelease -y -
Follow normal Fedora build and release process.