Hysen Labskubeadm-certs
kubeadm-certs sets the validity period of kubeadm certificate to 10 years. kubeadm-certs 将 kubeadm 的证书有效期设置为10年。
kubeadm-certs
A rebuild of kubeadm that extends the certificate validity period to ten years, with no other source changes, matched release per Kubernetes version.
What it changes
kubeadm-certs only sets the kubeadm certificate validity period to ten years and makes no other modification to the source. The README points to the build script and CI in the repository, and the project releases versions matched to Kubernetes releases so a user downloads the binary for their specific cluster version. The change targets the certificate validity constants in the Kubernetes source rather than altering any behavior.
Usage
The workflow is to back up and replace the system kubeadm binary with the downloaded one for the matching Kubernetes version, then run kubeadm init phase certs all and kubeadm init phase kubeconfig all. The README shows the output of kubeadm certs check-expiration where every certificate, from admin.conf and apiserver to the certificate authorities, expires roughly nine years out, demonstrating the extended validity. The user should confirm the version matches their cluster before replacing the binary.
Go version mapping and notes
The README includes a table mapping each Kubernetes version to its minimum Go version, from v1.15.12 with go1.12.1 up through v1.34.0 with go1.24, which guides which toolchain builds a given release. The README also documents the sha256 sums of the modified and original binaries and notes the dirty GitCommit marker that appears because the source was modified after the official commit. The project is licensed MIT.
Editorial conclusion
kubeadm-certs is MIT licensed and reported forty nine stars at indexing, and the README documents sha256 sums plus a dirty marker to distinguish the modified binary from the official one.
Community notes