A Practical Guide to SIG Release Tooling for Kubernetes Subprojects
summary
Overview of exact release steps and tools: images build in GitHub-triggered pipelines and must use Google Cloud Build to push to a staging repo on registry.k8s.io, then require promotion via kpromo (forgotten promotions are the common failure mode); binaries default to GitHub Releases (pkgs.k8s.io exists but is limited); Debian/RPM packages publish through Open Build Service with RPM specs auto-converted to deb and builds consuming prebuilt artifacts; release-notes, bom and attestation tools generate changelogs, SBOMs and signed build metadata.
AI-written summary · about
chapters (13)
- 0:00SIG Release tooling intro
- 1:26SIG Release mission
- 3:14Hosting artifacts
- 5:02Container images on Registry K8s IO
- 8:59Binaries on GitHub Releases
- 10:04Debian/RPM on Packages K8s IO
- 13:33Enriching releases
- 14:38Release notes generation
- 17:27Dependency validation
- 18:28SBOMs with bom
- 19:53Attesting builds with slsa-verifier
- 20:37GitHub Actions workflows
- 21:01Q&A
related talks
38mSIG Release - Deep Dive: Release Engineering Subproject
35mFrom Kubernetes With ♥ Open Tools For Open, Secure Supply Chains
32mDeep Dive: Kubernetes (Release) SIG
33mA Day in the Life of Kubernetes Release with Tools, Challenges, and Operations
37mBuilding the Cloud Native Kernel: Kubernetes Release Engineering
19mKeynote: Releasing a More Mature and Stable Kubernetes
38mSIG Release Deep Dive
31mIntro to Kubernetes Sig-Architecture Subprojects