Skip to content
Branch: master
Find file Copy path
Find file Copy path
8 contributors

Users who have contributed to this file

@justaugustus @tpepper @nikhita @spiffxp @SlickNik @MaciekPytel @idealhack @hoegaarden
112 lines (76 sloc) 5.1 KB

Release Managers

Release Managers is an umbrella term that encompasses the set of Kubernetes contributors responsible for maintaining release branches, tagging releases, and building/packaging Kubernetes.

The responsibilities of each role are described below.


Mailing List Slack Visibility Usage Membership #release-management (channel) / @release-managers (user group) Public Public discussion for Release Managers All Release Managers (Patch Release Team, Branch Managers, Associates, Build Admins, SIG Chairs) #release-private Private Private discussion for privileged Release Managers Patch Release Team, Build Admins, SIG Chairs


Patch Release Team

The Patch Release Team is responsible for coordinating patch releases (x.y.z, where z >= 0) of Kubernetes. This team at times works in close conjunction with the Product Security Committee and therefore should abide by the guidelines set forth in the Security Release Process.

GitHub teams


Branch Managers

Branch Managers are responsible for minor releases (x.y.z, where z = 0) of Kubernetes, working in close conjunction with the Release Team through each release cycle.



Release Manager Associates are apprentices to the Branch Managers, formerly referred to as Branch Manager shadows.


Build Admins

Build Admins are (currently) Google employees with the requisite access to Google build systems/tooling to publish deb/rpm packages on behalf of the Kubernetes project.

GitHub team


SIG Release Chairs

SIG Release Chairs are responsible for the governance of SIG Release. They are mentioned explicitly here as they are owners of the various communications channels and permissions groups (GitHub teams, GCP access) for each role.

As such, they are highly privileged community members and privy to some private communications, which can at times relate to Kubernetes security disclosures.

GitHub team


Past Branch Managers, can be found in the releases directory within release-x.y/ Example: 1.15 Release Team

You can’t perform that action at this time.