Kubernetes Release Team: The Whys & Hows, Ways & Means!

The presentation discusses the release process of Kubernetes and the roles of different teams in the process.

• Different teams are involved in the release process of Kubernetes, including the release team, documentation team, and branch management team.
• The release team is responsible for creating a place to keep track of deprecated APIs, creating the official release blog, coordinating webinars, and generating and editing release notes.
• The documentation team helps create feature blocks and writes blogs about new features.
• The branch management team is responsible for cutting the release and promoting images.
• The shadow program is open to anyone and has no requirements or working hours.
• Handbooks are available for each role to guide new members.

The release team creates a theme and logo for each release of Kubernetes, with Star Trek themes being popular. The team also created a tool called Krell to scrape and create release notes, which was iterated on by other teams. The branch management team cuts the release and promotes images, with the help of Google for building RPMs and Deb packages. However, work is being done to remove the reliance on Google. The shadow program is open to anyone, regardless of experience, and handbooks are available to guide new members.

Are you curious about the inner workings of a project as huge as Kubernetes? Who are the people bringing you fresh Kubernetes releases thrice a year like clockwork? It's the Kubernetes Release Team! And do you want to be part of the Release Team? But you’re not aware of the different responsibilities & commitments needed and the many ways to contribute? Then this is *the* talk for you to get all those insights! The Kubernetes Release Team is a subproject under Kubernetes SIG Release and is responsible for the day to day work required to successfully produce Kubernetes releases on a reliable schedule, while the SIG as a whole works to enhance the release process. In this talk, we will discuss: * What the Kubernetes Release Team is, and what it isn't * Discuss all the different Release Team roles and processes * How we try to make things better with Release retrospective meetings * Outreach effort to increase diversity in the Release Team shadow program