Resources on Kubernetes Contributors

Community Calendar

Mon, 01 Jan 0001 00:00:00 +0000

Displayed times are in your local timezone

Services and Requests

Mon, 01 Jan 0001 00:00:00 +0000

GitHub requests
Communication platform and services
Other
- Netlify websites
- Funding

GitHub requests

Organization membership

Kubernetes GitHub Org members should be actively contributing to the upstream project, and should meet the general requirements outlined in the community membership guidelines .

Org membership requests can be made using the Org Membership Request form in the kubernetes/org repo. Requests are often processed in batch once every 2-3 business days.

Kubernetes v1.37 Release Information

Mon, 01 Jan 0001 00:00:00 +0000

Guides

Summary

The v1.37 release cycle is proposed as follows:

Monday 18th May 2026: Week 1 — Release cycle begins
Tuesday 9th June 2026 (AoE) / Wednesday 10th June 2026, 12:00 UTC: Week 4 — Production Readiness Freeze
Tuesday 16th June 2026 (AoE) / Wednesday 17th June 2026, 12:00 UTC: Week 5 — Enhancements Freeze
Thursday 18th - Friday 19th June 2026: Week 5 — KubeCon India
Thursday 9th July 2026 (AoE) / Friday 10th July 2026, 12:00 UTC: Week 8 — Feature blog freeze
Wednesday 22nd July 2026 (AoE) / Thursday 23rd July 2026, 12:00 UTC: Week 10 — Code Freeze and Test Freeze
Tuesday 28th - Thursday 30th July 2026: Week 11 — KubeCon Japan
Wednesday 5th August 2026 (AoE) / Thursday 6th August 2026, 12:00 UTC: Week 12 — Docs Freeze
Wednesday 26th August 2026: Week 15 — Kubernetes v1.37.0 released

[!NOTE] Deadlines are expressed in “Anywhere on Earth” (AoE) time. This means the date ends when the calendar day finishes in the last timezone on Earth (UTC-12). Example: A deadline of Thursday, Oct 16 (AoE) gives contributors their full Thursday everywhere in the world. The cutoff therefore would be Friday, Oct 17 at 12:00 UTC.

Default Branch Migration

Mon, 01 Jan 0001 00:00:00 +0000

This document outlines steps needed to migrate the default branch of your repo from master to main.

Note: This document is currently a work in progress.

If you have questions about the process, reach out to the GitHub Management Team on the #github-management channel on slack or open an issue in the kubernetes/org repo.

Prerequisites

Create an issue in your repo to track the branch rename. You can paste this checklist in the issue body.

Resources on Kubernetes Contributors

Community Calendar

Services and Requests

GitHub requests

Organization membership

Kubernetes v1.37 Release Information

Links

Guides

Summary

Default Branch Migration

Prerequisites