Why Kubernetes Is Shifting to a Three‑Release‑Per‑Year Cadence

Kubernetes' official blog announced that the release team has merged a Kubernetes Enhancement Proposal (KEP) to change the release cadence from four to three releases per year.

The adjustment is driven by the increasing number of enhancements per cycle, which adds burden to contributors and the release team, and by the challenges frequent updates pose for downstream users and vendors.

The new policy also aims to reduce SIG release and team overhead, allowing more focus on improving release quality and tooling.

What are the specific changes?

The first Kubernetes version of a calendar year should start in the second or third week of January, giving developers space after the winter break.

The final version of the year should be completed by mid‑December.

Each release cycle will be about 15 weeks long.

The week of KubeCon + CloudNativeCon is not considered a SIG release “working week”; no meetings or decisions are made then.

There will be a mandatory minimum two‑week SIG release blackout between cycles.

Consequently, Kubernetes will follow a three‑release‑per‑year rhythm, with version 1.23 being the final release of 2021. The article includes a predicted schedule based on this policy.

These dates reflect start and end times and may change; the release team will set exact freeze dates for each milestone, and the policy does not constitute an LTS.

For full details, see the official blog post at https://kubernetes.io/blog/2021/07/20/new-kubernetes-release-cadence/.