Welcome on Kubernetes Contributors

Kubernetes Meet and Greet

Thu, 01 Jan 2026 00:00:00 +0000

About

Grab your lunch and come join the Kubernetes Meet and Greet ! This event is for SIGs and WGs, new and experienced contributors. We will have representatives from many SIG / WG to answer questions and talk more about how to get involved.

The Kubernetes M&G is for both:

Experienced Kubernetes contributors who are interested in expanding their involvement in new SIGs / WGs, or just hanging out with their SIG/WG collaborators.
New contributors who are looking for where they can contribute to Kubernetes

Details

The Kubernetes Meet and Greet will take place on Wednesday, March 25, from noon to 3pm, in the Europe Foyer.

Maintainer Summit Europe 2026

Thu, 01 Jan 2026 00:00:00 +0000

About

The European edition of the Maintainer Summit will take place on Sunday, March 22, 2026, in Amsterdam, Netherlands, alongside KubeCon + CloudNativeCon Europe 2026.

The Summit is a dedicated day for maintainers to collaborate in person. The event will feature:

Submitted Talks: Technical deep dives and project health updates.
Unconference Sessions: Open-space discussions for spontaneous problem-solving and SIG alignment.
Documentation Sprint: A collaborative session focused on improving project resources.
Contributor Social: An evening of games and networking following the technical tracks.

📅 Schedule & Participation

Volunteer & Staffing: If you are interested in volunteering or staffing for this event, please see kubernetes/community#8819 .
Call for Proposals (CFP): Check the event schedule for submission deadlines.
Registration: Register here .

Eligibility

Who can attend Maintainer Summit?

2019 Awards

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

By Special Interest Group (SIG)

SIG Cloud Provider

Lubomir Ivanov

SIG Instrumentation

Han Kang

SIG Release

Katharine Berry

SIG Scheduling

Huang Wei

SIG Storage

Michelle Au

SIG Windows

Jordan Liggitt

WG Multitenancy

Ryan Bezdicek

2020 Awards

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

By Special Interest Group (SIG)

API Machinery

Haowei Cai
Chao Xu

Architecture

Hippie Hacker
Michelle Au
Dawn Chen
Paris Pittman

Authentication

Shihang Zhang

CLI

Yao Zhou
Brian Pursely
Syam Sundar Kirubakaran

Cloud Provider

Cici Huang

Contributor Experience

Matthew Broberg
Kaslin Fields
Noah Kantrowitz
Rajula Vineet Reddy

Cluster Lifecycle

Ciprian Hacman
John Gardiner Myers
Ole Markus

Documentation

Tim Bannister
Qiming Teng
Zachary Sarah Corleissen

Instrumentation

Hongcai Ren
Lili Cosic
Marek Siarkowicz

Network

Antonio Ojea
Jay Vyas

Release

Joyce Kung
Daniel Mangum

Scheduling

Aldo Culquicondor

Storage

Patrick Ohly

Testing

Antonio Ojea
Daniel Magnum

Usability

Gaby Moreno Cesar
Carl J Pearson
Josie Pynadath

Windows

James Sturtevant

2021 Awards

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

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Han Kang, @logicalhan
For their continued contributions related to the overlap with SIG Instrumentation.

Antoine Pelisse
For their long term effort and leadership on server-side-apply and the related wg-api-expression.

Apps

Aldo Culquicondor
For improving the jobs controller, expanding its functionality

Architecture

Riaan Kleinhans
Conformance Work

Madhav Jivrajani
KEP Reading Club

Kirsten Garrison, @kikisdeliveryservice
Enhancements Subproject

Elana Hashman, @ehashdn
Production Readiness Reviews

2022 Awards

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

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Joe Betz, @jpbetz
For his leadership and contributions introducing CEL as a powerful feature for Kubernetes, and leading the strategy and execution of all the subsequent projects like CRD Validation, Admission Control, and more to come.

Antonio Ojea, @aojea
For the long list of sustained contributions, especially for the cross-over from networking to apimachinery/client-go, picking up bug fixes, backports, and code reviews.

2023 Awards

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

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Mike Spreitzer, @MikeSpreitzer
For his continued contributions and relentless effort in designing, leading, implementing, and refining priority and fairness for the kube-apiserver.

Jeffrey Ying, @Jefftree
For his design and implementation work for aggregated discovery which improves all discovering clients for his design and implementation work for aggregated discovery which improves all discovering REST clients.

Apps

Michał Woźniak, @mimowo
Michał has been consistently contributing improvements and fixes to the job controller to improve its usage in various batch workloads.

2024 Awards

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

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Marek Siarkowicz, @serathius
Marek’s contributions to the Consistent Reads from Cache project over the past few years have been truly inspiring. This initiative required deep expertise in both etcd and Kubernetes, coupled with a steadfast determination to see it through to completion. Marek’s work has led to one of the most significant scalability improvements in recent years. Without his dedication and skill, this achievement would not have been possible.

2025 Awards

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

By Special Interest Group (SIG) with listed message/nomination reason

API Machinery

Aaron Prindle, @aaron-prindle
Aaron has been a driving force behind the new declarative validation framework in Kubernetes. His leadership and technical contributions to KEP-5073, which introduces validation-gen, have been instrumental in moving Kubernetes API validation from complex, handwritten Go code to a more maintainable and author-friendly declarative model. Over the last year, Aaron’s work has established the foundational infrastructure for this transition, including the creation of the validation-gen code generator. This work significantly lowers the barrier for new contributors and improves the overall quality and consistency of the Kubernetes API, making it a more robust and accessible project for the entire community.

Community Calendar

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

Displayed times are in your local timezone

How to Join

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

Notice

This event has passed. Recordings from the event can be found on the target="_blank" rel=“noopener”>Kubernetes Community YouTube Channel .

The celebration and all the activities will all take place on the official Kubernetes Discord server with major events being streamed to the Kubernetes YouTube Channel .

Register for the event
Connecting to Discord
- Create and verify your account
- Connecting to the server
Tips and suggestions for using Discord

Register for the event

Invites will be sent to people that register on Thursday, December 10th. If you register after that date, an invite will be sent shortly after you’ve signed up.

How to Join

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

Notice

This event has passed. Recordings from the event can be found on the target="_blank" rel=“noopener”>Kubernetes Community YouTube Channel .

The celebration and all the activities will all take place on the official Kubernetes Discord server with major events being streamed to the Kubernetes YouTube Channel .

Register for the event
Connecting to Discord
- Create and verify your account
- Connecting to the server
Tips and suggestions for using Discord

Register for the event

Invites will be sent to people that register closer to the event.

Section 1: Starting Out

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

Welcome to Kubernetes!

Welcome to the New Contributor course for Kubernetes!

Section 1: Starting Out

Each unit of this course consists of a slideshow and links to resources. Take your time reading the materials, and feel free to reach out to the community with questions.

We look forward to your contributions!

What you are about to learn

This first unit is all about starting out in the Kubernetes community. By the end of this unit, you will:

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.

Contributor Cheatsheet

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

A list of common resources when contributing to Kubernetes, tips, tricks, and common best practices used within the Kubernetes project. It is a “TL;DR” or quick reference of useful information to make your GitHub contribution experience better.

Table of Contents

Helpful Resources
Communicating Effectively on GitHub
- How to be Excellent to Each Other
  - Examples of Good/Bad Communication
Submitting a Contribution
Working Locally
- Branch Strategy

Helpful Resources

Getting Started

Contributor Course - NEW - The E-Learning for Contributors course for Kubernetes!
Contributor Guide - Guide on how to begin contributing to Kubernetes Project.
Developer Guide - Guide to contributing code directly to the Kubernetes Project.
Security and Disclosure Information - Guide for reporting vulnerabilities and the security release process.

SIGs and Other Groups

Master Group List

Community

Calendar - View all the Kubernetes Community events (SIG/WG meetings, events etc.)
kubernetes-dev - The Kubernetes development mailing list
Kubernetes Forum - Official Kubernetes forum.
Slack channels - Official Kubernetes Slack.
Stack Overflow - A place to ask your Kubernetes end-user questions.
YouTube Channel - Official channel for the Kubernetes community.

Workflow

Prow - Kubernetes CI/CD System.
Tide - Prow plugin that manages merges and tests. Tide Dashboard
Bot commands - Commands used to interact with Kubernetes Bots (examples: /cc, /lgtm, and /retest)
GitHub labels - List of labels used throughout the Kubernetes Project
Kubernetes Code Search , maintained by @dims

Tests

Prow - Kubernetes CI/CD System.
Test Grid - View historical tests and their associated information.
Triage Dashboard - Aggregates similar failures together for better troubleshooting.

Important Email Aliases

community@kubernetes.io - Mail someone on the community team (SIG Contributor Experience) about a community issue.
conduct@kubernetes.io - Contact the Code of Conduct committee, private mailing list.
github@kubernetes.io - Mail the GitHub Administration Team privately, for sensitive items.
steering@kubernetes.io - Mail the steering committee. Public address with public archive.
steering-private@kubernetes.io - Mail the steering committee privately, for sensitive items.
social@cncf.io - Contact the CNCF social team; blog, twitter account, and other social properties.

Communicating Effectively on GitHub

How to be Excellent to Each Other

As a first step, familiarize yourself with the Code of Conduct .

Events and Activities

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

Notice

This event has passed. Recordings from the event can be found on the target="_blank" rel=“noopener”>Kubernetes Community YouTube Channel .

NOTE: This list is not complete or final, there will be room for more :)

Events
Party Games
Board Games
Virtual Photobooth

Events

Kubernetes Contributor Awards

Session link

Kubernetes SIG Co-Chairs and Tech Leads would like for you to attend this special event where we honor and dedicate the hard work that the community has been working on. These peer awards are a tradition at the Kubernetes Contributor Summits so we are bringing them virtual, please join us to thank and support all the people who have worked hard to help us this year.

Events and Activities

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

Notice

This event has passed. Recordings from the event can be found on the target="_blank" rel=“noopener”>Kubernetes Community YouTube Channel .

NOTE: This list is not complete or final, there will be room for more :)

Events

Events

Kubernetes Contributor Awards

Kubernetes Community Values

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

Kubernetes Community culture contributes substantially to the project’s success. The following values have evolved over time, pushing our project and peers toward constant improvement.

Distribution is better than centralization

The scale of the Kubernetes project is only viable through high-trust and high-visibility distribution of work, which includes delegation of authority, decision making, technical design, code ownership, and documentation. Distributed asynchronous ownership, collaboration, communication and decision making are the cornerstones of our world-wide community.

Registration

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

Registration is open to all members of one of the Kubernetes orgs or sponsored attendees.

Register Here

If you are not yet a member, but active within the project, please consider joining! The process of joining is straight forward. See our org membership docs for more information. If your application to join is pending, please contact us at community@kubernetes.io about registering.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines requiring ALL in-person attendees to be fully vaccinated against the COVID-19 virus.

Registration

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

Registration is open to all members of one of the Kubernetes orgs or sponsored attendees.

Registration will close on October 20th.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines requiring ALL in-person attendees to be fully vaccinated against the COVID-19 virus or to show proof of a negative COVID-19 test administered by a verified provider.

Registration

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

Registration is open to all members of one of the Kubernetes orgs .

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines

If you acknowledge the above, please go ahead and click below to register:

Registration

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

Registration is open to all members of one of the Kubernetes orgs or sponsored attendees.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines

If you acknowledge the above, please go ahead and click below to register:

Registration

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

Registration is open to all members of one of the Kubernetes orgs , qualified Etcd contributors, or sponsored attendees. Registration closes: Thursday, November 2nd, 2023; 16:00 US Eastern Time

Registration

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

Registration is open to all members of one of the Kubernetes orgs or sponsored attendees.

NOTE: The summit adheres to KubeCon’s Health & Safety Guidelines

If you acknowledge the above, please go ahead and click below to register:

Registration

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

Registration is open to all members of one of the Kubernetes orgs , qualified Etcd contributors, or sponsored attendees. Registration closes: Thursday, November 7th, 2024; 16:00 US Eastern Time

RSVP

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

As we are not holding the formal Contributor Summit, we are not running conference registration. SIGs and subprojects who choose to hold a mini-event will be responsible for any kind of signups they need to manage.

We will be holding an evening social event, however, and have an RSVP link for attendees. To attend the social, you must be a member or active contributor of one of the Kubernetes GitHub Orgs (e.g., kubernetes or kubernetes-sigs ) or a sponsored attendee. If you are an active contributor but not a member, consider applying for org membership !

Schedule

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

Notice

This event has passed. Recordings from the event can be found on the target="_blank" rel=“noopener”>Kubernetes Community YouTube Channel .

Thursday December 10th, the doors will open and members will be invited to discord.

Events and official activities are planned for Friday and Saturday, with the server remaining open on Sunday for anyone that would still like to join in and hang out.

Kubernetes Contributor Celebration

Schedule

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

Notice

This event has passed. Recordings from the event can be found on the target="_blank" rel=“noopener”>Kubernetes Community YouTube Channel .

Kubernetes Contributor Celebration

Section 2: Getting Into GitHub

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

Section 2: Getting Into GitHub

What you’re about to learn

The first step to being a Kubernetes contributor is getting into GitHub! After this unit, you will:

Understand GitHub capabilities and how Kubernetes uses it
Understand fork and clone and be able to perform these on a repository
Be able to complete the contributor license agreement (CLA) and make a first pull request

What is GitHub?

GitHub is a web service for managing software development with Git.
It provides bug tracking, task management, hosted development environments, continuous integration, and other important features .
GitHub hosts the source code for many open source projects, including Kubernetes.

Working with GitHub is straightforward, but if you are new to it, it can seem complex. We want to make the process as easy as possible for you!

Making your First Contribution

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

Find something to work on

Find something to work on

The first step to getting starting contributing to Kubernetes is to find something to work on. Help is always welcome, and no contribution is too small (but see below)!

Mentoring Programs and Resources

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

This page indexes all of the mentoring initiatives for contributing to the Kubernetes project. For end user mentoring initiatives, check out KubeCon and other CNCF events and programs.

We understand that everyone has different learning styles and we want to support as many of those as possible. Mentoring is vital to the growth of an individual and organization of every kind. For Kubernetes, the larger the project becomes , it’s necessary to keep a continuous pipeline of quality contributors and we want you to hang around!

Schedule

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

NOTE: You must go through vaccine verification and pick up your badge before attending the summit or social evening event.

Steering AMA

The Summit will start off with an AMA with members of the Kubernetes Steering Committee. Bring any and all questions about how we’re running the project, ongoing efforts & issues, and whatever you’d like to discuss with Steering.

Unconference

The Contributor Summit will be an Unconference-style event . This means that you should arrive with topics in mind, and we will pitch them and vote on them in the morning, and then hold sessions in the afternoon, after the Steering AMA. This is the format used at many DevOps Days , and helps us accommodate changing needs and unpredictable travel schedules.

Schedule

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

Kubernetes Contributor Summit Europe 2022

Schedule

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

NOTE: You MUST pick up your badge before attending the summit event.

Schedule

Tuesday, September 26th

09:00 ~ 09:15 am - Welcome: Kevin Wang (Huawei Cloud)/Puja (Gaint Swarm)
09:15 ~ 09:45 am - #sig-multi-cluster : Technical thinking, practice, and planning of multi-cluster management in the Kubernetes community by Hongcai Ren (Huawei Cloud, Karmada Maintainer)
09:45 ~ 10:15 am - Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases: Helmfile by Xiongxiong Yuan (Gitlab China)
10:15 ~ 10:30 am - Break/Networking (Tea break) & Group Photo
10:30 ~ 11:00 am - #sig-scheduling : Kubernetes Scheduling Updates and Future: Leibo Wang (Huawei Cloud)
11:00 ~ 12:30 am - Unconference
Lunch & Networking

Unconference

The unconference sessions coming soon! If you have a topic in mind, please check back soon - we’ll launch a tracking issue for submissions closer to the event.

Schedule

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

NOTE: You MUST pick up your badge before attending the summit or social evening event.

Steering AMA

Unconference

The Contributor Summit will be primarily an Unconference-style event . This means that you should arrive with topics in mind, and we will pitch them and vote on them in the morning, and then hold sessions in the afternoon, after the Steering AMA. This is the format used at many DevOps Days , and helps us accommodate changing needs and unpredictable travel schedules.

Schedule

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

NOTE: You MUST pick up your badge before attending the summit or social evening event.

CFP

A CFP for sessions is open through Friday, September 15th. Please, expect the schedule to be announced on October 6th, 2023.

Steering AMA

Schedule

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

NOTE: You MUST pick up your badge before attending the summit or social evening event.

Steering AMA

Unconference

The Contributor Summit will include one track of Unconference-style sessions .
After the CfP closes, contributors will be able to pitch and vote on last-minute sessions in a GitHub Issue, and final selection of those topics will be made at the Summit itself. This allows us to incorporate community issues and ideas that come to light after the CfP ends.

Schedule

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

NOTE: You MUST pick up your badge before attending the summit or social evening event.

CFP

The Cfp is closed. You can still propose topics in the Unconference sessions. See below for the kinds of session proposals which are appropriate.

Steering AMA

Section 3: Pull Requests

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

Section 3: Pull Requests

Objectives

This unit will teach you all about how to submit and manage pull requests for the different Kubernetes repositories. By the end of this unit, you will be able to:

Reference and operate in the Kubernetes GitHub workflow
Recognize common bots and their messages
Respond to code comments and test failures

What is a pull request?

Before we start teaching you how to use pull requests, we should tell you what they are!

Contributing to Kubernetes

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

Communication
GitHub workflow
Open a Pull Request
Code Review
Best Practices
Testing
Security
Documentation
Issues Management or Triage

Kubernetes is open source, but many of the people working on it do so as their day job. In order to avoid forcing people to be “at work” effectively 24/7, we want to establish some semi-formal protocols around development. Hopefully, these rules make things go more smoothly. If you find that this is not the case, please complain loudly.

Frequently Asked Questions (FAQ)

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

Notice

This event has passed. Recordings from the event can be found on the target="_blank" rel=“noopener”>Kubernetes Community YouTube Channel .

General Information
Discord Information

General Information

What is the Kubernetes Contributor Celebration?

The Kubernetes Contributor Celebration is an attempt to reclaim that and celebrate our accomplishments. It’s a time for us to relax, chat and do something fun with your fellow contributors!

Frequently Asked Questions (FAQ)

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

Notice

This event has passed. Recordings from the event can be found on the target="_blank" rel=“noopener”>Kubernetes Community YouTube Channel .

General Information
Discord Information

General Information

What is the Kubernetes Contributor Celebration?

The Kubernetes Contributor Celebration is an attempt to reclaim that and celebrate our accomplishments. It’s a time for us to relax, chat and do something fun with your fellow contributors!

Frequently Asked Questions (FAQ)

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

When is the summit taking place?
Where is the summit located?
Will I be able to attend remotely?
Why is vaccination required to attend in-person?
Why do I need to be a Kubernetes Org member to attend in-person?
What is a sponsored attendee?
I am not an Org member. Can I still attend?
Will there be a New Contributor Workshop?
I have a question! How do I contact the event staff?

When is the summit taking place?

October 11th, the Monday before KubeCon North America .

Location & Venue

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

Feria Valencia

Registration and badge pick-up will be available at the Feria Valencia. You MUST go through vaccination verification and pick up your badge before attending the summit or evening social event.

The summit itself will be on Level 3 of the Feria Valencia Event Center. Masking is required.

Address
Av. de les Fires, s/n, 46035
València, Spain

La Casa de la Mar

The Contributor Social will be held at the La Casa de la Mar several kilometers from the Feria. CNCF will be providing a bus from the Fiera to the venue, and our community will also organize ride-sharing. Details to be posted later. Masking and vaccination are required for the party.

Location & Venue

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

Huntington Place

Registration and badge pick-up will be available at the Huntington Place Convention Center. You MUST pick up your badge before attending the summit or evening social event.

Address
1 Washington Blvd
Detroit, MI 48226

Deluxx Fluxx

The evening social will be held at Deluxx Fluxx, a short walk away from the convention center.

Address
1274 Library St
Detroit, MI 48226

Location & Venue

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

Shanghai Convention & Exhibition Center Of International Sourcing

Registration and badge pick-up will be available at the Shanghai Convention & Exhibition Center Of International Sourcing. You MUST pick up your badge before attending the summit event.

The summit itself will be in the Shanghai Convention & Exhibition Center Of International Sourcing. Masks are recommended, but not required for event attendees. Some masks will be available.

Address
No.2739 West Guangfu Road, Putuo District, Shanghai (200062)

Location & Venue

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

RAI Amsterdam

Registration and badge pick-up will be available at the RAI Amsterdam. You MUST pick up your badge before attending the summit or evening social event.

The summit itself will be in the RAI Amsterdam Convention Centre. Masks are recommended, but not required for event attendees. Some masks will be available.

Address
Europaplein 24, 1078 GZ
Amsterdam, Netherlands

The Contributor Social will be held at Strandzuid , next to the Convention Centre.

Location & Venue

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

Hyatt Regency McCormick Place

Registration and badge pick-up will be available at the Hyatt Regency McCormick Place. You MUST pick up your badge before attending the summit or evening social event.

The summit will be in the Hyatt Regency McCormick Place. Masks are recommended, but not required for event attendees. Some masks will be available.

Address
2233 South Dr. Martin Luther King Jr. Drive
Chicago, Illinois, 60616-9985, USA

The Contributor Social will be held on the evening of the 6th, at a location to be determined.

Location & Venue

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

Porte de Paris - Paris Convention Center

You MUST pick up your badge before attending the Contributor Summit or evening social event.

The summit will be in the Porte de Paris - Paris Convention Center. Masks are recommended, but not required for event attendees. Some masks will be available. In Pavilion 7 Floor 3 West

Address
1 Place de la Porte de Versailles
75015 Paris, France

Drop-off The center is located at 1 Place de la Porte de Versailles

Location & Venue

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

Salt Palace Convention Center

Registration and badge pick-up will be available at the Salt Palace Convention Center. You MUST pick up your badge before attending the summit or evening social event.

The summit will be in the Salt Palace Convention Center. Masks are recommended, but not required for event attendees.

Address
90 South West Temple
Salt Lake City, Utah 84101

The Contributor Social will be held from 6pm - 9pm on November 11th, at Flanker.

Section 4: Issues Management and Triage

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

Section 4: Issues Management/Triage

What you’re about to learn

This unit will help you get started with issue management across the Kubernetes GitHub repositories. By the end, you’ll:

Understand and locate the issues management and triage tags
Know where bugs are reported and how they are triaged
Be able to understand how to prioritize work based on issues
Be able to locate the security response committee for security issues

How does Kubernetes use GitHub issues?

Contributors and end users use issues for a variety of reasons:

Contributor Social

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

From 6:30 to 8:30pm (and beyond), Kubernetes contributors will be schmoozing, eating, playing boardgames, and competing in a pub quiz at La Casa Del Mar , a cafe and bar by the beach in Valencia.

The Social is open only to registered attendees of the Kubernetes Contributor Summit and possibly their guests (see below). You must be registered before attending.

Contributor Social

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

Join us at Deluxx Fluxx Detroit from 6pm to 9pm for an evening celebration after the Contributor Summit on October 24th!

There will be arcade cabinets, foosball, karaoke, trivia and more!

The contributor social is not a public event. You must be registered in advance to attend the Contributor Summit in order to attend the Social, and must be a Kubernetes contributor. Community members who are not registered and show up at the Social will be turned away.

Contributor Social

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

Join us at Strandzuid from 6pm to 9pm for an evening celebration after the Contributor Summit on April 18th!

There will be food, fresh air, puzzles, and more!

Contributor Social

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

Join us for the Contributor Social from 6pm to 9pm for an evening celebration after the Contributor Summit on November 6th!

There will be food, live music, activities, and more!

Contributor Social

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

Join us at La Serre from 6pm to 9pm for an evening celebration after the Contributor Summit on March 19th!

There will be food, fresh air, puzzles, and more!

The Summit will include a social event open only to Contributors (and their family members, see Guests below). This event will take place somewhere near the Summit venue, and will include food, drink, entertainment, and games. More information will be available once the venue is booked.

Contributor Social

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

Join us at Flanker from 6pm to 9pm for an evening celebration after the Contributor Summit on November 11th!

There will be food, live music, activities, and more!

Location & Venue

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

Marriott

The North America Summit will take place October 11th, in Los Angeles, California alongside KubeCon at the JW Marriott LA Live in Ballroom 6. There will be signage in the Marriott Lobby to point you in the right direction.

Address
JW Marriott Los Angeles L.A. LIVE
900 West Olympic Boulevard
Los Angeles, California 90015 USA

Lucky Strike

The evening social event will be held at Lucky Strike, a bowling alley, 1 block away from the Marriott.

Platforms Guide

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

Adding supported platforms

The default Kubernetes platform is linux/amd64. This platform has always been fully tested, and the build and release systems initially supported only this platform. SIG Release started an effort to support multiple architectures . As part of this effort, they added support in our build and release pipelines for the architectures arm, arm64, ppc64le and s390x on different operating systems like Linux, Windows and macOS.

The main focus was to have binaries and container images to be available for these architectures/operating systems. Contributors should be able to to take these artifacts and set up CI jobs to adequately test these platforms. Specifically to call out the ability to run conformance tests on these platforms.

Pull Request Process

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

This doc explains the process and best practices for submitting a pull request to the Kubernetes project and its associated sub-repositories. It should serve as a reference for all contributors, and be useful especially to new and infrequent submitters.

Before You Submit a Pull Request
- Run Local Verifications
The Pull Request Submit Process
Why was my pull request closed?
Why is my pull request not getting reviewed?
Best Practices for Faster Reviews
The Testing and Merge Workflow
- More About Ok-To-Test

Before You Submit a Pull Request

This guide is for contributors who already have a pull request to submit. If you’re looking for information on setting up your developer environment and creating code to contribute to Kubernetes, see the development guide .

Section 5: Getting Started with Kubernetes Development

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

Section 5: Getting Started with Kubernetes Development

What you’re about to learn

It’s time to set up a development environment so you can build Kubernetes. By end of this unit, you will:

Know the various environments for building and developing Kubernetes
Know where to find the Kubernetes Development Guide

What are your options for a development environment?

There are three primary options, all with their own benefits and drawbacks.

Building Kubernetes with Docker
Building Kubernetes on your local OS and shell environment
Building Kubernetes with GitHub Codespaces

Why build with Docker?

This method uses a containerized build environment. There are some good reasons to use it:

GitHub Workflow

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

1. Fork in the cloud

Visit https://github.com/kubernetes/kubernetes
Click Fork button (top right) to establish a cloud-based fork.

2. Clone fork to local storage

In your shell, define a local working directory as working_dir.

export working_dir="${HOME}/src/k8s.io" # Change to your preferred location for source code

Set user to match your github profile name:

export user=<your github profile name>

Both $working_dir and $user are mentioned in the figure above.

Create your clone:

mkdir -p $working_dir
cd $working_dir
git clone https://github.com/$user/kubernetes.git
# or: git clone git@github.com:$user/kubernetes.git

cd $working_dir/kubernetes
git remote add upstream https://github.com/kubernetes/kubernetes.git
# or: git remote add upstream git@github.com:kubernetes/kubernetes.git

# Never push to upstream master
git remote set-url --push upstream no_push

# Confirm that your remotes make sense:
git remote -v

3. Create a Working Branch

Get your local master up to date. Note that depending on which repository you are working from, the default branch may be called “main” instead of “master”.

Schedule

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

NOTE: You must go through vaccine verification and pick up your badge before attending the summit or social evening event.

October 10th

2pm - 6pm - Registration + Vaccine Verification + Badge Pick-up @ the LACC

October 11th

8am - 6pm - Registration + Vaccine Verification + Badge Pick-up @ the LACC
9am - 4pm - Contributor hangout @ the Marriott (ballroom 6)
5pm - 8pm - Evening social with bowling and billiards @ Lucky Strike

Section 6: Testing

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

Section 6: Testing

This unit is all about the various types of tests, both automated and manual, in the Kubernetes project.

What you’re about to learn

By the time you’re done with this unit, you’ll:

Be able to locate the requirements for manual testing during development
Be able to respond to the automatic tests of bots for a pull request

Testing Kubernetes is pretty complicated. We will try to make it easy for you, but you might want to start by reading the Development Guide .

Frequently Asked Questions (FAQ)

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

When is the summit taking place?
Where is the summit located?
Will I be able to attend remotely?
Why is vaccination required to attend in-person?
Do I need to wear a mask?
Why do I need to be a Kubernetes Org member to attend in-person?
What is a sponsored attendee?
I am not an Org member. Can I still attend?
I have an idea for a session. How do I propose it?
My SIG wants to meet at the Summit
Will there be a Doc Sprint?
Will there be a New Contributor Workshop?
Can I bring a guest to the Contributor Social
I have a question! How do I contact the event staff?

When is the summit taking place?

May 16th, the Monday of KubeCon Europe .

Frequently Asked Questions (FAQ)

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

When is the summit taking place?
Where is the summit located?
Will I be able to attend remotely?
Do I need to wear a mask?
Why do I need to be a Kubernetes Org member to attend in-person?
What is a sponsored attendee?
I am not an Org member. Can I still attend?
I have an idea for a session. How do I propose it?
My SIG wants to meet at the Summit
Will there be a Doc Sprint?
Will there be a New Contributor Workshop?
Can I bring a guest to the Contributor Social
I have a question! How do I contact the event staff?

When is the summit taking place?

October 24th, the Monday of KubeCon North America .

Frequently Asked Questions (FAQ)

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

When is the summit taking place?
Where is the summit located?
Will I be able to attend remotely?
What are the Health and Safety protocols?
Priority Registration Notice: Org Members for Contributor Summit
I have an idea for a session
Will there be a New Contributor Workshop?
I have a question! How do I contact the event staff?

When is the summit taking place?

September 26th, the first day of KubeCon + CloudNativeCon + Open Source Summit China 2023 .

Frequently Asked Questions (FAQ)

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

When is the summit taking place?
Where is the summit located?
Will I be able to attend remotely?
What are the Health and Safety protocols
Why do I need to be a Kubernetes Org member to attend in-person?
What is a sponsored attendee?
I have an idea for a session
My SIG wants to meet at the Summit
Will there be a doc sprint?
Will there be a New Contributor Workshop?
Can I bring a guest to the Social?
I have a question! How do I contact the event staff?

When is the summit taking place?

April 18th, the first day of KubeCon Europe .

Frequently Asked Questions (FAQ)

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

When is the summit taking place?
Where is the summit located?
Will I be able to attend remotely?
What are the Health and Safety protocols
Why do I need to be a Kubernetes Org member to attend in-person?
What is a sponsored attendee?
I have an idea for a session
My SIG wants to meet at the Summit
Will there be a doc sprint?
Will there be a New Contributor Workshop?
Can I bring a guest to the Social?
I have a question! How do I contact the event staff?

When is the summit taking place?

November 6th, the first day of KubeCon North America .

Frequently Asked Questions (FAQ)

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

When is the summit taking place?
Where is the summit located?
Will I be able to attend remotely?
What are the Health and Safety protocols
Why do I need to be a Kubernetes Org member to attend in-person?
What is a sponsored attendee?
I have an idea for a session
My SIG wants to meet at the Summit
Will there be a doc sprint?
Will there be a New Contributor Workshop?
Can I bring a guest to the Social?
I have a question! How do I contact the event staff?

When is the summit taking place?

March 19, 2024

Frequently Asked Questions (FAQ)

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

When is the summit taking place?
Where is the summit located?
Will I be able to attend remotely?
What are the Health and Safety protocols
Why do I need to be a Kubernetes Org member to attend in-person?
What is a sponsored attendee?
Do I need to be registered for KubeCon to attend the Contributor Summit
I have an idea for a session
My SIG wants to meet at the Summit
Will there be a doc sprint?
Will there be a New Contributor Workshop?
Can I bring a guest to the Social?
I have a question! How do I contact the event staff?

When is the summit taking place?

November 11th, one day prior to KubeCon North America .

Section 7: Code Review

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

Section 7: Code Review

What you’re about to learn

In this unit, you will learn everything about getting your code contributions to Kubernetes reviewed. By the end of this unit, you will be able to:

Understand the role of code reviews in the lifecycle of a pull request.
Use your SIG process to get a senior contributor to review code for approval.

What is a code review?

A code review is when other developers examine proposed changes and additions to source code.

Coding Conventions

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

Code conventions

Bash
- Shell Style Guide
- Ensure that build, release, test, and cluster-management scripts run on macOS
Go
- Go Code Review Comments
- Effective Go
- Know and avoid Go landmines
- Comment your code.
  - Go’s commenting conventions
  - If reviewers ask questions about why the code is the way it is, that’s a sign that comments might be helpful.
- Command-line flags should use dashes, not underscores
- Naming
  - Please consider package name when selecting an interface name, and avoid redundancy. For example, storage.Interface is better than storage.StorageInterface.
  - Do not use uppercase characters, underscores, or dashes in package names.
  - Please consider parent directory name when choosing a package name. For example, pkg/controllers/autoscaler/foo.go should say package autoscaler not package autoscalercontroller.
    - Unless there’s a good reason, the package foo line should match the name of the directory in which the .go file exists.
    - Importers can use a different name if they need to disambiguate.
  - Locks should be called lock and should never be embedded (always lock sync.Mutex). When multiple locks are present, give each lock a distinct name following Go conventions: stateLock, mapLock etc.
- API changes
- API conventions
- Kubectl conventions
- Logging conventions

Testing conventions

All new packages and most new significant functionality must come with unit tests.
Table-driven tests are preferred for testing multiple scenarios/inputs. For an example, see TestNamespaceAuthorization .
Significant features should come with integration (test/integration) and/or end-to-end (test/e2e) tests .
- Including new kubectl commands and major features of existing commands.
Unit tests must pass on macOS and Windows platforms - if you use Linux specific features, your test case must either be skipped on windows or compiled out (skipped is better when running Linux specific commands, compiled out is required when your code does not compile on Windows).
Avoid relying on Docker Hub. Use the Google Cloud Artifact Registry instead.
Do not expect an asynchronous thing to happen immediately—do not wait for one second and expect a pod to be running. Wait and retry instead.
See the testing guide for additional testing advice.

Directory and file conventions

Avoid package sprawl. Find an appropriate subdirectory for new packages. See issue #4851 for discussion.
- Libraries with no appropriate home belong in new package subdirectories of pkg/util.
Avoid general utility packages. Packages called “util” are suspect. Instead, derive a name that describes your desired function. For example, the utility functions dealing with waiting for operations are in the wait package and include functionality like Poll. The full name is wait.Poll.
All filenames should be lowercase.
Go source files and directories use underscores, not dashes.
- Package directories should generally avoid using separators as much as possible. When package names are multiple words, they usually should be in nested subdirectories.
Document directories and filenames should use dashes rather than underscores.
Examples should also illustrate best practices for configuration and using the system .
Follow these conventions for third-party code:
- Go code for normal third-party dependencies is managed using go modules and is described in the kubernetes vendoring guide .
- Other third-party code belongs in third_party.
  - forked third party Go code goes in third_party/forked.
  - forked golang stdlib code goes in third_party/forked/golang.
- Third-party code must include licenses. This includes modified third-party code and excerpts, as well.

Section 8: Community

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

Section 8: Community

What you’re about to learn

It’s time to learn about communication and community among Kubernetes contributors. By the end of this unit, you will:

Understand the size, diversity, and capability of the Kubernetes community
Be able to interact with members productively
When to use email, when to use Slack, when to use GitHub issues, etc.
Know the venues for involvement, including Kubecon and SIG meetings.

How big is the Kubernetes contributor community?

The Kubernetes community has thousands of active contributors.

Help Wanted and Good First Issue Labels

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

Overview

We use two labels to identify issues that have been specifically created or selected for new contributors: help wanted and good first issue . The good first issue label is a subset of the help wanted label, indicating that members have committed to providing extra assistance for new contributors. All good first issue items also have the help wanted label.

We also have some suggestions for using these labels to help grow and improve our community.

Section 9: Documentation

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

Section 9: Documentation

What you’re about to learn

This unit is about documentation, and by the end, you will:

Know where documentation is stored for Kubernetes
Understand the importance of localization
Understand the process and responsibilities for updating documentation
Know who is responsible for documentation
Locate the style guide and other guidance for writing documentation

How is the Kubernetes documentation organized?

The documentation for the Kubernetes project can be divided into a number of categories.

Issue Triage Guidelines

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

Scope
What Is Triaging?
Why Is Triaging Beneficial?
How to Triage: A Step-by-Step Flow
- Triage-Related Tools
- Process Pointers and Advice from SIGs
  - Running a Triage Meeting: Tips from api-machinery
  - Triage Guide by cluster-lifecycle
Step One: Review Newly Created Open Issues
- Conducting Searches
Step Two: Triage Issues by Type
Step Three: Define Priority
Step Four: Find and Set the Right SIG(s) to Own an Issue
- Self-Assigning
Step Five: Follow Up
Further Notes
- Support Requests: Channels
- User Support Response: Example

Scope

These guidelines serve as a primary document for triaging incoming issues to Kubernetes. SIGs and projects are encouraged to use this guidance as a starting point, and customize to address specific triaging needs.

NCO Host Handbook

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

Host Responsibilities

Any active contributor with org membership is invited to participate in New Contributor Orientation (NCO) meetings as a host. A host is an active contributor who participates in NCO by helping to answer attendee questions about contribution based on that host’s own unique experience contributing to the project.

The goal of the New Contributor Orientation meeting is to help prospective new contributors find their way in the Kubernetes community by providing them with basic information about the community to help orient them within it, and to provide some mentorship through Q&A with existing contributors. Hosts should keep the audience in mind, and gear their answers to help the attendees find their own path in the community.

Section 10: Architecture and Enhancements

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

Section 10: Architecture and Enhancements

What you’re about to learn

We’re getting into the guts of Kubernetes now! After this module, you will:

Be able to locate the architecture documents for Kubernetes
Understand how the different components interact
Know how features and major changes are added to Kubernetes

Where are the architecture documents?

The good news is that the Kubernetes architecture is very well documented.

A great place to start is this overview of Kubernetes components .
You can find the cluster architecture in the Concepts section of the documentation .

What are the components of a Kubernetes cluster?

A Kubernetes deployment is called a cluster. So what is it made of?

Non-code Contributions

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

This section is new and in progress. Expect this document to change often.

If you are interested in helping define and structure this work, check the weekly meeting notes for information on how to get involved. You can also find us in the SIG Contributor Experience Slack channel .

All contributors welcome, new and old!

What is this?

The list below is meant to help non-code contributors find areas of the Kubernetes project where their expertise can be best utilized. The goal of this is to both provide a starting guide for anyone looking to become a contributor not necessarily writing code, and also to fill any needs that the SIGs have that might not currently be filled by code-focused contributors.

Adding Release Notes

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

On the kubernetes/kubernetes repository , release notes are required for any pull request with user-visible changes, this could mean:

User facing, critical bug-fixes
Notable feature additions
Output format changes
Deprecations or removals
Metrics changes
Dependency changes
API changes

Release notes are one of the most important reference points for users about to install or upgrade to a particular release of Kubernetes.

Does my pull request need a release note?

Any user-visible or operator-visible change qualifies for a release note. This could be a:

OWNERS Files

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

Overview

OWNERS files are used to designate responsibility over different parts of the Kubernetes codebase. Today, we use them to assign the reviewer and approver roles (defined in our community membership doc ) that are used in our two-phase code review process. Our OWNERS files were inspired by Chromium OWNERS files which in turn inspired GitHub’s CODEOWNERS files

The velocity of a project that uses code review is limited by the number of people capable of reviewing code. The quality of a person’s code review is limited by their familiarity with the code under review. Our goal is to address both of these concerns through the prudent use and maintenance of OWNERS files.

Community Expectations

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

Kubernetes is a community project. Consequently, it is wholly dependent on its community to provide a productive, friendly and collaborative environment.

The first and foremost goal of the Kubernetes community is to develop orchestration technology that radically simplifies the process of creating reliable distributed systems. However a second, equally important goal is the creation of a community that fosters easy, agile development of such orchestration systems.

We therefore describe the expectations for members of the Kubernetes community. This document is intended to be a living one that evolves as the community evolves via the same PR and code review process that shapes the rest of the project. It currently covers the expectations of conduct that govern all members of the community as well as the expectations around code review that govern all active contributors to Kubernetes.

NCO Lead Handbook

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

Meeting Lead Roles

The NCO meeting Lead is responsible for running the NCO meeting for at least 1 [monthly] session. Each NCO Lead is responsible for identifying at least 1 NCO Lead to succeed them.

NCO Lead Pre-requisites

Kubernetes Org Membership
- The NCO meeting lead must be an active contributor.
- An NCO Lead should also be active on the Kubernetes Slack
Availability to lead at least 1 meeting in at least 1 month
Attend at least 1 NCO session or have watched at least 1 recording of an NCO session
Interest in helping new and prospective contributors find their way in the community

NCO Lead Responsibilities

Determine the time of the monthly session
- Coordinate with sig-contribex leads (sig-contribex-leads@kubernetes.io ) if meeting times need to be changed from the standard schedule.
Create and configure meeting materials for the lead’s session(s)
- Create a new slide deck for the session based on either the previous month’s session or the template
- Contact SIG Leads to update the “Calls for Help” section in the session. Comms should be sent to SIG leads at least one week in advance via the chairs-and-techleads channel in Slack and the leads@kubernetes.io mailing list.
Publish the meeting content in this repo’s nco-slides folder at least 1 day before the session is held
- Publishing the meeting content in advance of the meeting will make the content more accessible to prospective attendees, and allow them to judge the value of the meeting in advance.
Lead the NCO Meeting
- Each NCO meeting agenda should consist of roughly 40min of presented content followed by roughly 20min of freeform Q&A. The lead is responsible for keeping track of time to ensure the meeting sticks roughly to the scheduled agenda. Both the presentation and Q&A portions of the meeting are important for delivering on the goals of the NCO initiative.
- If the lead will not give the presentation themselves, they are responsible for identifying a host who will give the presentation effectively and efficiently.
Identify at least 1 succeeding lead
- If you are unable to identify a lead to succeed you, contact the sig-contribex leads (sig-contribex-leads@kubernetes.io ) as early as is reasonable.

Determining Meeting Time(s)

NCO Meetings aim to make contribution more accessible to anyone interested in it. As such, meetings should take into account accessibility in different timezones around the world. Typically, this requires running the meeting at least twice. The recommended schedule for sessions is:

New Contributor Resources

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

Join the Community

Join the Kubernetes Developer Google Group (k-dev): https://groups.google.com/a/kubernetes.io/g/dev
Check out kubernetes/community for an overview of our community.
Come join us in the Kubernetes Slack :
- Join the #kubernetes-new-contributors channel
- Join the channels of 1 or more SIGs you’re interested in
Participate in the New Contributor Orientation to get an introduction to Kubernetes development and the community.

Getting Familiar with the Process

Follow the Contributor Guide to get familiar with various contributor tools and processes.
Read The First Contribution Guide for a walkthrough of your first Pull Request (PR) process.

Additional Resources

Explore the comprehensive Resources List at https://bit.ly/kubernetes-resources

CRI API version skew policy

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

CRI is a plugin interface which enables the kubelet to use a wide variety of container runtimes, without the need to recompile. CRI consists of a protocol buffers and gRPC API. Read more about CRI API at kubernetes docs .

The CRI API is only intended to be used for the kubelet to container runtime interactions, or for node-level troubleshooting using a tool such as crictl. It is not a common purpose container runtime API for general use, and is intended to be Kubernetes-centric. This is why there may be an undocumented logic within a container runtimes that assumes the order or specific parameters of call(s) that the kubelet makes. Attempts to call CRI API in a different order by a client different than the kubelet, might result in unrecoverable error. Whenever discovered, this logic is being documented and avoided.

Kubernetes feature development and container runtimes

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

The mechanics of a feature development that requires new CRI APIs is covered in documentation on CRI API feature-development . This article defines policies for developing new Kubernetes features that require CRI API changes. The goal of these policies is to ensure great user experience for people trying the new feature early, adopting it when it is enabled by default, and relying on it as a GA functionality.

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.

Code Of Conduct

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

Kubernetes follows the CNCF Code of Conduct .

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Kubernetes Code of Conduct Committee via conduct@kubernetes.io .

The text of the CNCF Code of Conduct is available below.

CNCF Community Code of Conduct v1.3

Other languages available:

Community Code of Conduct

As contributors, maintainers, and participants in the CNCF community, and in the interest of fostering an open and welcoming community, we pledge to respect all people who participate or contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, attending conferences or events, or engaging in other community or project activities.

Code of Conduct Committee Incident Reporting and Response Process

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

This document outlines the Code of Conduct Committee’s workflow when receiving and responding to an incident report. As each report is unique, the process is described at a high level.

When and Where does the Kubernetes Code of Conduct apply?

The Code of Conduct applies between all community members when interacting about Kubernetes. This primarily addresses official spaces, but if conduct-related issues are affecting our community in unofficial spaces in ways that are likely also affect interpersonal interactions in official spaces, we may be asked to become involved.

KCD Around the World: New York

Tue, 28 Jul 2026 10:00:00 -0800

Welcome to KCD Around the World, a new series where we explore Kubernetes Community Days from every corner of the globe. When most people think of KCD, they think about talks and technical sessions, but behind every event is a community of volunteers, contributors, organizers and attendees who make it all happen. Through conversations with the people behind each KCD, we’ll share what makes it unique.

Our first stop: New York City. To learn what made this year’s event special, we interview Christopher Tineo, one of the organizers for KCD NY 2026.

From Working Group to SIG Architecture: spotlight on AI Conformance

Thu, 09 Jul 2026 00:00:00 +0000

In this SIG Architecture spotlight we talked with Janet Kuo (Google) and Yuan Tang (Red Hat) about the journey of AI Conformance in Kubernetes, from the initial Working Group to the integration SIG Architecture as a subproject.

Introductions

Frederico Muñoz and Kirti Goyal (FK): Hi Janet, Yuan, and thank you for the opportunity to learn a bit more about AI Conformance. Can you tell us a bit about yourselves and how you got involved in Kubernetes?

Human-Centered Automation for Kubernetes Localization in the AI Era

Fri, 26 Jun 2026 14:00:00 -0800

This year, the Kubernetes localization subproject participated in LFX Mentorship for the first time through the project “CNCF - Kubernetes: SIG Docs Localization: AI-era localization automation” . The work was also tracked in kubernetes/website#54075 .

As the mentee on this project, I worked with Kubernetes SIG Docs localization mentors on a practical maintenance question:

In an era of rapidly improving AI translation tools, what kind of automation actually helps localization maintainers?

Kubernetes documentation is used by readers around the world. Localization helps make the project more accessible to users and contributors by providing content in their native languages. But localization is not only about translating pages once. It is also about maintaining those pages as Kubernetes changes.

Open source maintainership in the age of AI

Fri, 26 Jun 2026 10:00:00 -0800

AI has really changed the game around software development. More people are leveraging AI than ever to contribute patches to projects they use. To me, this is a good thing as more folks will contribute patches rather than fork or not fix them. The main problem is that AI has made generating code fast but there has been very little improvement in maintaining code bases. In this post, we will highlight the ways the Kubernetes community is adapting to the world of AI assisted coding.

Spotlight on WG Device Management

Wed, 24 Jun 2026 10:00:00 -0800

The rising popularity of AI, Edge, and Telecommunications workloads on Kubernetes has led to new requirements for hardware management. We now need hardware specification beyond CPU time and memory allocations. This includes allocating GPUs, TPUs, network interfaces, and other hardware, sometimes after pod start and occasionally through time-sharing.

Efficiently managing this specialized hardware is the mission of the Device Management Working Group . Their cornerstone project, Dynamic Resource Allocation (DRA) , recently graduated to GA, marking a fundamental shift in how the project handles hardware-intensive workloads at scale.

Spotlight on SIG Storage

Mon, 15 Jun 2026 00:00:00 +0000

In our ongoing SIG Spotlight series, we shine a light on the groups that keep the Kubernetes project moving forward. This time, we catch up with SIG Storage , the group responsible for persistent data, volume management, and the interfaces that connect Kubernetes workloads to the storage systems beneath them.

We spoke with Xing Yang , Co-Chair of SIG Storage and Software Engineer at VMware by Broadcom, about the SIG’s history, the features shipping in recent Kubernetes releases, and where storage in Kubernetes is headed as AI workloads become the norm.

Eliminating Kubernetes Image Signature Replication

Fri, 05 Jun 2026 00:00:00 +0000

The image promoter rewrite laid the groundwork for simplifying how Kubernetes delivers container image signatures. One of the rewrite phases (Phase 6) separated image signing from signature replication into distinct pipeline stages. This follow-up covers the next step: eliminating signature replication entirely.

The problem

After promoting container images to registry.k8s.io, the promoter signs them using cosign with keyless (OIDC) signatures. These signatures are stored as OCI artifacts alongside the images, tagged with the convention sha256-<digest>.sig and sha256-<digest>.att.

Announcing the AI Gateway Working Group

Mon, 09 Mar 2026 00:00:00 +0000

The community around Kubernetes includes a number of Special Interest Groups (SIGs) and Working Groups (WGs) facilitating discussions on important topics between interested contributors. Today, we’re excited to announce the formation of the AI Gateway Working Group , a new initiative focused on developing standards and best practices for networking infrastructure that supports AI workloads in Kubernetes environments.

What is an AI Gateway?

In a Kubernetes context, an AI Gateway refers to network gateway infrastructure (including proxy servers, load-balancers, etc.) that generally implements the Gateway API specification with enhanced capabilities for AI workloads. Rather than defining a distinct product category, AI Gateways describe infrastructure designed to enforce policy on AI traffic, including:

Spotlight on SIG Architecture: API Governance

Thu, 12 Feb 2026 00:00:00 +0000

This is the fifth interview of a SIG Architecture Spotlight series that covers the different subprojects, and we will be covering SIG Architecture: API Governance .

In this SIG Architecture spotlight we talked with Jordan Liggitt , lead of the API Governance sub-project.

Introduction

FM: Hello Jordan, thank you for your availability. Tell us a bit about yourself, your role and how you got involved in Kubernetes.

JL: My name is Jordan Liggitt. I’m a Christian, husband, father of four, software engineer at Google by day, and amateur musician by stealth. I was born in Texas (and still like to claim it as my point of origin), but I’ve lived in North Carolina for most of my life.

Announcing the Checkpoint/Restore Working Group

Wed, 21 Jan 2026 00:00:00 +0000

The community around Kubernetes includes a number of Special Interest Groups (SIGs) and Working Groups (WGs) facilitating discussions on important topics between interested contributors. Today we would like to announce the new Kubernetes Checkpoint Restore WG focusing on the integration of Checkpoint/Restore functionality into Kubernetes.

Motivation and use cases

There are several high-level scenarios discussed in the working group:

Optimizing resource utilization for interactive workloads, such as Jupyter notebooks and AI chatbots
Accelerating startup of applications with long initialization times, including Java applications and LLM inference services
Using periodic checkpointing to enable fault-tolerance for long-running workloads, such as distributed model training
Providing interruption-aware scheduling with transparent checkpoint/restore, allowing lower-priority Pods to be preempted while preserving the runtime state of applications
Facilitating Pod migration across nodes for load balancing and maintenance, without disrupting workloads.
Enabling forensic checkpointing to investigate and analyze security incidents such as cyberattacks, data breaches, and unauthorized access.

Across these scenarios, the goal is to help facilitate discussions of ideas between the Kubernetes community and the growing Checkpoint/Restore in Userspace (CRIU) ecosystem. The CRIU community includes several projects that support these use cases, including:

Ingress NGINX Retirement: What You Need to Know

Wed, 12 Nov 2025 12:00:00 -0500

To prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX . Best-effort maintenance will continue until March 2026. Afterward, there will be no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered. Existing deployments of Ingress NGINX will continue to function and installation artifacts will remain available.

We recommend migrating to one of the many alternatives. Consider migrating to Gateway API , the modern replacement for Ingress. If you must continue using Ingress, many alternative Ingress controllers are listed in the Kubernetes documentation . Continue reading for further information about the history and current state of Ingress NGINX, as well as next steps.

Announcing the 2025 Steering Committee Election Results

Sun, 09 Nov 2025 15:10:00 -0500

The 2025 Steering Committee Election is now complete. The Kubernetes Steering Committee consists of 7 seats, 4 of which were up for election in 2025. Incoming committee members serve a term of 2 years, and all members are elected by the Kubernetes Community.

The Steering Committee oversees the governance of the entire Kubernetes project. With that great power comes great responsibility. You can learn more about the steering committee’s role in their charter .

Spotlight on Policy Working Group

Sat, 18 Oct 2025 00:00:00 +0000

(Note: The Policy Working Group has completed its mission and is no longer active. This article reflects its work, accomplishments, and insights into how a working group operates.)

In the complex world of Kubernetes, policies play a crucial role in managing and securing clusters. But have you ever wondered how these policies are developed, implemented, and standardized across the Kubernetes ecosystem? To answer that, let’s take a look back at the work of the Policy Working Group.

Spotlight on the Kubernetes Steering Committee

Mon, 22 Sep 2025 00:00:00 +0000

This interview was conducted in August 2024, and due to the dynamic nature of the Steering Committee membership and election process it might not represent the actual composition accurately. The topics covered are, however, overwhelmingly relevant to understand its scope of work. As we approach the Steering Committee elections, it provides useful insights into the workings of the Committee.

The Kubernetes Steering Committee is the backbone of the Kubernetes project, ensuring that its vibrant community and governance structures operate smoothly and effectively. While the technical brilliance of Kubernetes is often spotlighted through its Special Interest Groups (SIGs) and Working Groups (WGs) , the unsung heroes quietly steering the ship are the members of the Steering Committee. They tackle complex organizational challenges, empower contributors, and foster the thriving open source ecosystem that Kubernetes is celebrated for.

Post-Quantum Cryptography in Kubernetes

Fri, 18 Jul 2025 00:00:00 +0000

The world of cryptography is on the cusp of a major shift with the advent of quantum computing. While powerful quantum computers are still largely theoretical for many applications, their potential to break current cryptographic standards is a serious concern, especially for long-lived systems. This is where Post-Quantum Cryptography (PQC) comes in. In this article, I'll dive into what PQC means for TLS and, more specifically, for the Kubernetes ecosystem. I’ll explain what the (suprising) state of PQC in Kubernetes is and what the implications are for current and future clusters.

Changes to Kubernetes Slack

Mon, 16 Jun 2025 00:00:00 +0000

UPDATE: We’ve received notice from Salesforce that our Slack workspace WILL NOT BE DOWNGRADED on June 20th. Stand by for more details, but for now, there is no urgency to back up private channels or direct messages.

~~Kubernetes Slack will lose its special status and will be changing into a standard free Slack on June 20, 2025~~. Sometime later this year, our community may move to a new platform. If you are responsible for a channel or private channel, or a member of a User Group, you will need to take some actions as soon as you can.

Spotlight on SIG Apps

Wed, 12 Mar 2025 00:00:00 +0000

In our ongoing SIG Spotlight series, we dive into the heart of the Kubernetes project by talking to the leaders of its various Special Interest Groups (SIGs). This time, we focus on SIG Apps , the group responsible for everything related to developing, deploying, and operating applications on Kubernetes. Sandipan Panda (DevZero ) had the opportunity to interview Maciej Szulik (Defense Unicorns ) and Janet Kuo (Google ), the chairs and tech leads of SIG Apps. They shared their experiences, challenges, and visions for the future of application management within the Kubernetes ecosystem.

Spotlight on SIG etcd

Tue, 04 Mar 2025 00:00:00 +0000

In this SIG etcd spotlight we talked with James Blair , Marek Siarkowicz , Wenjia Zhang , and Benjamin Wang to learn a bit more about this Kubernetes Special Interest Group.

Introducing SIG etcd

Frederico: Hello, thank you for the time! Let’s start with some introductions, could you tell us a bit about yourself, your role and how you got involved in Kubernetes.

Benjamin: Hello, I am Benjamin. I am a SIG etcd Tech Lead and one of the etcd maintainers. I work for VMware, which is part of the Broadcom group. I got involved in Kubernetes & etcd & CSI (Container Storage Interface ) because of work and also a big passion for open source. I have been working on Kubernetes & etcd (and also CSI) since 2020.

Spotlight on SIG Architecture: Enhancements

Tue, 21 Jan 2025 00:00:00 +0000

This is the fourth interview of a SIG Architecture Spotlight series that will cover the different subprojects, and we will be covering SIG Architecture: Enhancements .

In this SIG Architecture spotlight we talked with Kirsten Garrison , lead of the Enhancements subproject.

The Enhancements subproject

Frederico (FSM): Hi Kirsten, very happy to have the opportunity to talk about the Enhancements subproject. Let’s start with some quick information about yourself and your role.

Spotlight on Kubernetes Upstream Training in Japan

Mon, 28 Oct 2024 00:00:00 +0000

We are organizers of Kubernetes Upstream Training in Japan . Our team is composed of members who actively contribute to Kubernetes, including individuals who hold roles such as member, reviewer, approver, and chair.

Our goal is to increase the number of Kubernetes contributors and foster the growth of the community. While Kubernetes community is friendly and collaborative, newcomers may find the first step of contributing to be a bit challenging. Our training program aims to lower that barrier and create an environment where even beginners can participate smoothly.

Announcing the 2024 Steering Committee Election Results

Wed, 02 Oct 2024 15:10:00 -0500

The 2024 Steering Committee Election is now complete. The Kubernetes Steering Committee consists of 7 seats, 3 of which were up for election in 2024. Incoming committee members serve a term of 2 years, and all members are elected by the Kubernetes Community.

This community body is significant since it oversees the governance of the entire Kubernetes project. With that great power comes great responsibility. You can learn more about the steering committee’s role in their charter .

Spotlight on CNCF Deaf and Hard-of-hearing Working Group (DHHWG)

Mon, 30 Sep 2024 00:00:00 +0000

In recognition of Deaf Awareness Month and the importance of inclusivity in the tech community, we are spotlighting Catherine Paganini , facilitator and one of the founding members of CNCF Deaf and Hard-of-Hearing Working Group (DHHWG). In this interview, Sandeep Kanabar , a deaf member of the DHHWG and part of the Kubernetes SIG ContribEx Communications team , sits down with Catherine to explore the impact of the DHHWG on cloud native projects like Kubernetes.

Spotlight on SIG Scheduling

Tue, 24 Sep 2024 00:00:00 +0000

In this SIG Scheduling spotlight we talked with Kensei Nakada , an approver in SIG Scheduling.

Introductions

Arvind: Hello, thank you for the opportunity to learn more about SIG Scheduling! Would you like to introduce yourself and tell us a bit about your role, and how you got involved with Kubernetes?

Kensei: Hi, thanks for the opportunity! I’m Kensei Nakada (@sanposhiho ), a software engineer at Tetrate.io . I have been contributing to Kubernetes in my free time for more than 3 years, and now I’m an approver of SIG Scheduling in Kubernetes. Also, I’m a founder/owner of two SIG subprojects, kube-scheduler-simulator and kube-scheduler-wasm-extension .

Spotlight on SIG API Machinery

Wed, 07 Aug 2024 00:00:00 +0000

We recently talked with Federico Bongiovanni (Google) and David Eads (Red Hat), Chairs of SIG API Machinery, to know a bit more about this Kubernetes Special Interest Group.

Introductions

Frederico (FSM): Hello, and thank your for your time. To start with, could you tell us about yourselves and how you got involved in Kubernetes?

David: I started working on OpenShift (the Red Hat distribution of Kubernetes) in the fall of 2014 and got involved pretty quickly in API Machinery. My first PRs were fixing kube-apiserver error messages and from there I branched out to kubectl (kubeconfigs are my fault!), auth (RBAC and *Review APIs are ports from OpenShift), apps (workqueues and sharedinformers for example). Don’t tell the others, but API Machinery is still my favorite :)

Spotlight on SIG Node

Thu, 20 Jun 2024 00:00:00 +0000

In the world of container orchestration, Kubernetes reigns supreme, powering some of the most complex and dynamic applications across the globe. Behind the scenes, a network of Special Interest Groups (SIGs) drives Kubernetes’ innovation and stability.

Today, I have the privilege of speaking with Matthias Bertschy , Gunju Kim , and Sergey Kanzhelev , members of SIG Node , who will shed some light on their roles, challenges, and the exciting developments within SIG Node.

Introducing Hydrophone

Thu, 23 May 2024 00:00:00 +0000

In the ever-changing landscape of Kubernetes, ensuring that clusters operate as intended is essential. This is where conformance testing becomes crucial, verifying that a Kubernetes cluster meets the required standards set by the community. Today, we’re thrilled to introduce Hydrophone , a lightweight runner designed to streamline Kubernetes tests using the official conformance images released by the Kubernetes release team.

Simplified Kubernetes testing with Hydrophone

Hydrophone’s design philosophy centers around ease of use. By starting the conformance image as a pod within the conformance namespace, Hydrophone waits for the tests to conclude, then prints and exports the results. This approach offers a hassle-free method for running either individual tests or the entire Conformance Test Suite .

Spotlight on SIG Architecture: Code Organization

Thu, 11 Apr 2024 00:00:00 +0000

This is the third interview of a SIG Architecture Spotlight series that will cover the different subprojects. We will cover SIG Architecture: Code Organization .

In this SIG Architecture spotlight I talked with Madhav Jivrajani (VMware), a member of the Code Organization subproject.

Introducing the Code Organization subproject

Frederico (FSM): Hello Madhav, thank you for your availability. Could you start by telling us a bit about yourself, your role and how you got involved in Kubernetes?

Using Go workspaces in Kubernetes

Tue, 19 Mar 2024 08:30:00 -0800

The Go programming language has played a huge role in the success of Kubernetes. As Kubernetes has grown, matured, and pushed the bounds of what “regular” projects do, the Go project team has also grown and evolved the language and tools. In recent releases, Go introduced a feature called “workspaces” which was aimed at making projects like Kubernetes easier to manage.

We’ve just completed a major effort to adopt workspaces in Kubernetes, and the results are great. Our codebase is simpler and less error-prone, and we’re no longer off on our own technology island.

Spotlight on SIG Cloud Provider

Fri, 01 Mar 2024 00:00:00 +0000

One of the most popular ways developers use Kubernetes-related services is via cloud providers, but have you ever wondered how cloud providers can do that? How does this whole process of integration of Kubernetes to various cloud providers happen? To answer that, let’s put the spotlight on SIG Cloud Provider .

SIG Cloud Provider works to create seamless integrations between Kubernetes and various cloud providers. Their mission? Keeping the Kubernetes ecosystem fair and open for all. By setting clear standards and requirements, they ensure every cloud provider plays nicely with Kubernetes. It is their responsibility to configure cluster components to enable cloud provider integrations.

A look into the Kubernetes Book Club

Thu, 22 Feb 2024 00:00:00 +0000

Learning Kubernetes and the entire ecosystem of technologies around it is not without its challenges. In this interview, we will talk with Carlos Santana (AWS) to learn a bit more about how he created the Kubernetes Book Club , how it works, and how anyone can join in to take advantage of a community-based learning experience.

Frederico Muñoz (FSM): Hello Carlos, thank you so much for your availability. To start with, could you tell us a bit about yourself?

Spotlight on SIG Release (Release Team Subproject)

Mon, 15 Jan 2024 00:00:00 +0000

The Release Special Interest Group (SIG Release), where Kubernetes sharpens its blade with cutting-edge features and bug fixes every 4 months. Have you ever considered how such a big project like Kubernetes manages its timeline so efficiently to release its new version, or how the internal workings of the Release Team look like? If you’re curious about these questions or want to know more and get involved with the work SIG Release does, read on!

Blixt - A load-balancer written in Rust, using eBPF, born from Gateway API

Mon, 08 Jan 2024 00:00:00 +0000

In SIG Network we now have a layer 4 (“L4”) load balancer named Blixt . This project started as a fun experiment using emerging technologies and is intended to become a utility for CI and testing to help facilitate the continued development of Gateway API . Are you interested in developing networking tools in Rust and eBPF ? Or perhaps you’re specifically interested in Gateway API? We’ll tell you a bit about the project and how it might benefit you.

Kubernetes supports running kube-proxy in an unprivileged container

Fri, 05 Jan 2024 00:00:00 +0000

This post describes how the --init-only flag to kube-proxy can be used to run the main kube-proxy container in a stricter securityContext, by performing the configuration that requires privileged mode in a separate init container . Since Windows doesn’t have the equivalent of capabilities, this only works on Linux.

The kube-proxy Pod still only meets the privileged Pod Security Standard , but there is still an improvement because the running container doesn’t need to run privileged.

Contextual logging in Kubernetes 1.29: Better troubleshooting and enhanced logging

Wed, 20 Dec 2023 09:30:00 -0800

On behalf of the Structured Logging Working Group and SIG Instrumentation , we are pleased to announce that the contextual logging feature introduced in Kubernetes v1.24 has now been successfully migrated to two components (kube-scheduler and kube-controller-manager) as well as some directories. This feature aims to provide more useful logs for better troubleshooting of Kubernetes and to empower developers to enhance Kubernetes.

What is contextual logging?

Contextual logging is based on the go-logr API. The key idea is that libraries are passed a logger instance by their caller and use that for logging instead of accessing a global logger. The binary decides the logging implementation, not the libraries. The go-logr API is designed around structured logging and supports attaching additional information to a logger.

Spotlight on SIG Testing

Fri, 24 Nov 2023 00:00:00 +0000

Welcome to another edition of the SIG spotlight blog series, where we highlight the incredible work being done by various Special Interest Groups (SIGs) within the Kubernetes project. In this edition, we turn our attention to SIG Testing , a group interested in effective testing of Kubernetes and automating away project toil. SIG Testing focus on creating and running tools and infrastructure that make it easier for the community to write and run tests, and to contribute, analyze and act upon test results.

Kubernetes Contributor Summit: Behind-the-scenes

Fri, 03 Nov 2023 00:00:00 +0000

Every year, just before the official start of KubeCon+CloudNativeCon, there’s a special event that has a very special place in the hearts of those organizing and participating in it: the Kubernetes Contributor Summit. To find out why, and to provide a behind-the-scenes perspective, we interview Noah Abrahams, whom amongst other roles was the co-lead for the Kubernetes Contributor Summit in 2023.

Frederico Muñoz (FSM): Hello Noah, and welcome. Could you start by introducing yourself and telling us how you got involved in Kubernetes?

Spotlight on SIG Architecture: Production Readiness

Thu, 02 Nov 2023 00:00:00 +0000

This is the second interview of a SIG Architecture Spotlight series that will cover the different subprojects. In this blog, we will cover the SIG Architecture: Production Readiness subproject .

In this SIG Architecture spotlight, we talked with Wojciech Tyczynski (Google), lead of the Production Readiness subproject.

About SIG Architecture and the Production Readiness subproject

Frederico (FSM): Hello Wojciech, could you tell us a bit about yourself, your role and how you got involved in Kubernetes?

A Quick Recap of 2023 China Kubernetes Contributor Summit

Fri, 20 Oct 2023 00:00:00 +0000

On September 26, 2023, the first day of KubeCon + CloudNativeCon + Open Source Summit China 2023 , nearly 50 contributors gathered in Shanghai for the Kubernetes Contributor Summit.

All participants in the 2023 Kubernetes Contributor Summit

This marked the first in-person offline gathering held in China after three years of the pandemic.

A joyful meetup

The event began with welcome speeches from Kevin Wang from Huawei Cloud, one of the co-chairs of KubeCon, and Puja from Giant Swarm.

Spotlight on SIG Architecture: Conformance

Thu, 05 Oct 2023 00:00:00 +0000

This is the first interview of a SIG Architecture Spotlight series that will cover the different subprojects. We start with the SIG Architecture: Conformance subproject

In this SIG Architecture spotlight, we talked with Riaan Kleinhans (ii-Team), Lead for the Conformance sub-project .

About SIG Architecture and the Conformance subproject

Frederico (FSM): Hello Riaan, and welcome! For starters, tell us a bit about yourself, your role and how you got involved in Kubernetes.

Riaan Kleinhans (RK): Hi! My name is Riaan Kleinhans and I live in South Africa. I am the Project manager for the ii-Team in New Zealand. When I joined ii the plan was to move to New Zealand in April 2020 and then Covid happened. Fortunately, being a flexible and dynamic team we were able to make it work remotely and in very different time zones.

Announcing the 2023 Steering Committee Election Results

Mon, 02 Oct 2023 00:00:00 +0000

The 2023 Steering Committee Election is now complete. The Kubernetes Steering Committee consists of 7 seats, 4 of which were up for election in 2023. Incoming committee members serve a term of 2 years, and all members are elected by the Kubernetes Community.

Spotlight on SIG ContribEx

Mon, 14 Aug 2023 00:00:00 +0000

Author: Fyka Ansari

Welcome to the world of Kubernetes and its vibrant contributor community! In this blog post, we’ll be shining a spotlight on the Special Interest Group for Contributor Experience (SIG ContribEx), an essential component of the Kubernetes project.

SIG ContribEx in Kubernetes is responsible for developing and maintaining a healthy and productive community of contributors to the project. This involves identifying and addressing bottlenecks that may hinder the project’s growth and feature velocity, such as pull request latency and the number of open pull requests and issues.

Spotlight on SIG CLI

Thu, 20 Jul 2023 00:00:00 +0000

In the world of Kubernetes, managing containerized applications at scale requires powerful and efficient tools. The command-line interface (CLI) is an integral part of any developer or operator’s toolkit, offering a convenient and flexible way to interact with a Kubernetes cluster.

SIG CLI plays a crucial role in improving the Kubernetes CLI experience by focusing on the development and enhancement of kubectl, the primary command-line tool for Kubernetes.

In this SIG CLI Spotlight, Arpit Agrawal, SIG ContribEx-Comms team member, talked with Katrina Verey , Tech Lead & Chair of SIG CLI,and Maciej Szulik , SIG CLI Batch Lead, about SIG CLI, current projects, challenges and how anyone can get involved.

Spotlight on SIG Network

Tue, 09 May 2023 00:00:00 +0000

Networking is one of the core pillars of Kubernetes, and the Special Interest Group for Networking (SIG Network) is responsible for developing and maintaining the networking features of Kubernetes. It covers all aspects to ensure Kubernetes provides a reliable and scalable network infrastructure for containerized applications.

In this SIG Network spotlight, Sujay Dey talked with Shane Utt , Software Engineer at Kong, chair of SIG Network and maintainer of Gateway API, on different aspects of the SIG, what are the exciting things going on and how anyone can get involved and contribute here.

E2E Testing Best Practices, Reloaded

Wed, 12 Apr 2023 00:00:00 +0000

End-to-end (E2E) testing in Kubernetes is how the project validates functionality with real clusters. Contributors sooner or later encounter it when asked to write E2E tests for new features or to help with debugging test failures. Cluster admins or vendors might run the conformance tests, a subset of all tests in the E2E test suite .

The underlying E2E framework for writing these E2E tests has been around for a long time. Functionality was added to it as needed, leading to code that became hard to maintain and use. The testing commons WG started cleaning it up, but dissolved before completely achieving their goals.

From Zero to Kubernets Subproject Lead

Wed, 29 Mar 2023 00:00:00 +0000

Getting started in any open-source community can be daunting, especially if it’s a big one like Kubernetes. I wrote this post to share my experience and encourage others to join up. All it takes is some curiosity and a willingness to show up!

Here’s how my journey unfolded at a high level:

What am I interested in? Is there a SIG (Special Interest Group) or a WG (Working Group) that is dedicated to that topic, or something similar?
Sign up for their mailing list and start hopping on meetings.
When (never if!) there are opportunities to help out and it aligns with your skills and desired growth areas, raise your hand.
Ask for lots of help and don’t be shy about not knowing everything (or anything!)
Keep plugging along, even if progress isn’t as fast as you would like it to be.

Starting up

First things first. What are you interested in learning more about? There are so many wonderful SIGs and working groups in the Kubernetes community: there’s something for everyone. And continuing to show up and participate will be so much easier if you think what you are doing is interesting. Likewise, continued participation is what keeps the community thriving, so that interest will drive you to have more of an impact.

Introducing KWOK: Kubernetes WithOut Kubelet

Wed, 01 Mar 2023 00:00:00 +0000

Author: Shiming Zhang (DaoCloud), Wei Huang (Apple), Yibo Zhuang (Apple)

Have you ever wondered how to set up a cluster of thousands of nodes just in seconds, how to simulate real nodes with a low resource footprint, and how to test your Kubernetes controller at scale without spending much on infrastructure?

If you answered “yes” to any of these questions, then you might be interested in KWOK, a toolkit that enables you to create a cluster of thousands of nodes in seconds.

Spotlight on SIG Instrumentation

Fri, 03 Feb 2023 00:00:00 +0000

Observability requires the right data at the right time for the right consumer (human or piece of software) to make the right decision. In the context of Kubernetes, having best practices for cluster observability across all Kubernetes components is crucial.

SIG Instrumentation helps to address this issue by providing best practices and tools that all other SIGs use to instrument Kubernetes components-like the API server, scheduler, kubelet and kube-controller-manager.

In this SIG Instrumentation spotlight, Imran Noor Mohamed , SIG ContribEx-Comms tech lead talked with Elana Hashman , and Han Kang , chairs of SIG Instrumentation, on how the SIG is organized, what are the current challenges and how anyone can get involved and contribute.

Prow and Tide for Kubernetes Contributors

Mon, 12 Dec 2022 00:00:00 +0000

Authors: Chris Short , Frederico Muñoz

In my work in the Kubernetes world, I look up a label or Prow command often. The systems behind the scenes (Prow and Tide ) are here to help Kubernetes Contributors get stuff done.

Labeling which SIG, WG, or subproject is as important as the issue or PR having someone assigned. To quote the docs , “Tide is a Prow component for managing a pool of GitHub PRs that match a given set of criteria. It will automatically retest PRs that meet the criteria (’tide comes in’) and automatically merge them when they have up-to-date passing test results (’tide goes out’).”

Implementing the Auto-refreshing Official Kubernetes CVE Feed

Mon, 12 Sep 2022 00:00:00 +0000

Author: Pushkar Joglekar (VMware)

Accompanying the release of Kubernetes v1.25, we announced availability of an official CVE feed as an alpha feature. This blog will cover how we implemented this feature.

Implementation Details

An auto-refreshing CVE feed allows users and implementers to programmatically fetch the list of CVEs announced by the Kubernetes SRC (Security Response Committee).

To ensure freshness and minimal maintainer overhead, the feed updates automatically by fetching the CVE related information from the CVE announcement GitHub Issues. Creating these issues is already part of the existing Security Response Committee (SRC) workflow.

Enhancements Opt-in Process Change for v1.26

Fri, 09 Sep 2022 00:00:00 +0000

Author: Grace Nguyen

Context and Motivations

Since the inception of the Kubernetes release team, we have used a spreadsheet to keep track of enhancements for the release. The project has scaled massively in the past few years, with almost a hundred enhancements collected for the 1.24 release. This process has become error-prone and time consuming. A lot of manual work is required from the release team and the SIG leads to populate KEPs data in the sheet. We have received continuous feedback from our contributors to streamline the process.

Spotlight on SIG Storage

Mon, 22 Aug 2022 00:00:00 +0000

Since the very beginning of Kubernetes, the topic of persistent data and how to address the requirement of stateful applications has been an important topic. Support for stateless deployments was natural, present from the start, and garnered attention, becoming very well-known. Work on better support for stateful applications was also present from early on, with each release increasing the scope of what could be run on Kubernetes.

Message queues, databases, clustered filesystems: these are some examples of the solutions that have different storage requirements and that are, today, increasingly deployed in Kubernetes. Dealing with ephemeral and persistent storage, local or remote, file or block, from many different vendors, while considering how to provide the needed resiliency and data consistency that users expect, all of this is under SIG Storage’s umbrella.

Meet Our Contributors - APAC (China region)

Mon, 15 Aug 2022 00:00:00 +0000

Authors & Interviewers: Avinesh Tripathi , Debabrata Panigrahi , Jayesh Srivastava , Priyanka Saggu , Purneswar Prasad , Vedant Kakde

Hello, everyone 👋

Welcome back to the third edition of the “Meet Our Contributors” blog post series for APAC.

This post features four outstanding contributors from China, who have played diverse leadership and community roles in the upstream Kubernetes project.

So, without further ado, let’s get straight to the article.

Andy Zhang

Andy Zhang currently works for Microsoft China at the Shanghai site. His main focus is on Kubernetes storage drivers. Andy started contributing to Kubernetes about 5 years ago.

Enhancing Kubernetes one KEP at a Time

Thu, 11 Aug 2022 00:00:00 +0000

Author: Ryler Hockenbury (Mastercard)

Did you know that Kubernetes v1.24 has 46 enhancements ? That’s a lot of new functionality packed into a 4-month release cycle. The Kubernetes release team coordinates the logistics of the release, from remediating test flakes to publishing updated docs. It’s a ton of work, but they always deliver.

The release team comprises around 30 people across six subteams - Bug Triage, CI Signal, Enhancements, Release Notes, Communications, and Docs. Each of these subteams manages a component of the release. This post will focus on the role of the enhancements subteam and how you can get involved.

Spotlight on SIG Docs

Tue, 02 Aug 2022 00:00:00 +0000

Author: Purneswar Prasad

Introduction

The official documentation is the go-to source for any open source project. For Kubernetes, it’s an ever-evolving Special Interest Group (SIG) with people constantly putting in their efforts to make details about the project easier to consume for new contributors and users. SIG Docs publishes the official documentation on kubernetes.io which includes, but is not limited to, documentation of the core APIs, core architectural details, and CLI tools shipped with the Kubernetes release.

Contextual Logging in Kubernetes 1.24

Wed, 25 May 2022 00:00:00 +0000

Authors: Patrick Ohly (Intel)

The Structured Logging Working Group has added new capabilities to the logging infrastructure in Kubernetes 1.24. This blog post explains how developers can take advantage of those to make log output more useful and how they can get involved with improving Kubernetes.

Structured logging

The goal of structured logging is to replace C-style formatting and the resulting opaque log strings with log entries that have a well-defined syntax for storing message and parameters separately, for example as a JSON struct.

February 2022 Community Meeting Highlights

Thu, 05 May 2022 00:00:00 +0000

Author: Nigel Brown (VMware)

We just had our first contributor community meeting this year, and it was awesome to be back with you in that format. These meetings will be happening on Zoom once per month, on the third Thursday of the month - that should be available in your calendar if you’re subscribed to the k-dev mailing list. Community meetings are an opportunity for you to meet synchronously with other members of the Kubernetes community to talk about issues of general appeal.

K8s CI Bot Helper Job: automating "make update"

Tue, 15 Mar 2022 00:00:00 +0000

Authors: Subhasmita Swain , Davanum Srinivas

If you are contributing to the Kubernetes project and are developing on a Windows PC, it is conceivable that you will encounter certain issues that will cause your pull request to get held up by test failures. This article describes a workaround for a similar issue I encountered when attempting to have my modifications approved and merged into the master branch.

Why is this needed?

While contributing to kubernetes/kubernetes for some minor documentation changes, the pushed changes needed to be updated with other verified contents of the entire documentation. So, in order for the change to take effect, a single command must be performed to ensure that all tests on the CI pipeline pass. The single command make update runs all presubmission verification tests. For some reason on the “Windows Subsystem for Linux” environment the tests, specifically the update-openapi-spec.sh script, failed (in my case, take a look at the conversation here ), eventually failing the pull-kubernetes-verify tests.

Meet Our Contributors - APAC (Aus-NZ region)

Mon, 14 Mar 2022 00:00:00 +0000

Authors & Interviewers: Anubhav Vardhan , Atharva Shinde , Avinesh Tripathi , Brad McCoy , Debabrata Panigrahi , Jayesh Srivastava , Kunal Verma , Pranshu Srivastava , Priyanka Saggu , Purneswar Prasad , Vedant Kakde

Good day, everyone 👋

Welcome back to the second episode of the “Meet Our Contributors” blog post series for APAC.

This post will feature four outstanding contributors from the Australia and New Zealand regions, who have played diverse leadership and community roles in the Upstream Kubernetes project.

SIG Node CI Subproject Celebrates Two Years of Test Improvements

Wed, 16 Feb 2022 00:00:00 +0000

Authors: Sergey Kanzhelev (Google), Elana Hashman (Red Hat)

Ensuring the reliability of SIG Node upstream code is a continuous effort that takes a lot of behind-the-scenes effort from many contributors. There are frequent releases of Kubernetes, base operating systems, container runtimes, and test infrastructure that result in a complex matrix that requires attention and steady investment to “keep the lights on.” In May 2020, the Kubernetes node special interest group (“SIG Node”) organized a new subproject for continuous integration (CI) for node-related code and tests. Since its inauguration, the SIG Node CI subproject has run a weekly meeting, and even the full hour is often not enough to complete triage of all bugs, test-related PRs and issues, and discuss all related ongoing work within the subgroup.

Spotlight on SIG Multicluster

Fri, 04 Feb 2022 00:00:00 +0000

Authors: Dewan Ahmed (Aiven) and Chris Short (AWS)

Introduction

SIG Multicluster is the Special Interest Group (SIG) focused on how Kubernetes concepts are expanded and used beyond the cluster boundary. Historically, Kubernetes resources only interacted within that boundary - KRU or Kubernetes Resource Universe (not an actual Kubernetes concept). Kubernetes clusters, even now, don’t really know anything about themselves or, about other clusters. Absence of cluster identifiers is a case in point. With the growing adoption of multicloud and multicluster deployments, the work SIG Multicluster doing is gaining a lot of attention.

Meet Our Contributors - APAC (India region)

Mon, 10 Jan 2022 00:00:00 +0000

Authors & Interviewers: Anubhav Vardhan , Atharva Shinde , Avinesh Tripathi , Debabrata Panigrahi , Kunal Verma , Pranshu Srivastava , Pritish Samal , Purneswar Prasad , Vedant Kakde

Editor: Priyanka Saggu

Good day, everyone 👋

Welcome to the first episode of the APAC edition of the “Meet Our Contributors” blog post series.

In this post, we’ll introduce you to five amazing folks from the India region who have been actively contributing to the upstream Kubernetes projects in a variety of ways, as well as being the leaders or maintainers of numerous community initiatives.

Announcing the Kubernetes Contributor Celebration 2021

Tue, 07 Dec 2021 00:00:00 +0000

Contributor Celebration 2021

It’s that time of the year again, Yayy!!

Like last year, this year also we are back with Kubernetes Contributor Celebration, the annual end of the year celebration, to recognize our achievements and have some fun! It’s a time for us to relax, chat and do something fun with your fellow contributors!

Registration

To register, please fill out the Registration Form . More details on how to join the event.

Improve your documentation with Mermaid.js diagrams

Wed, 01 Dec 2021 00:00:00 +0000

By Chris Metz and Tim Bannister

Topics covered in this blog.

Live editor link: Topics Covered

Why are diagrams useful for documentation?

Friendly landing spot. Greeting readers with a page full of text can be intimidating to those new to Kubernetes, software engineering and tech writing.
Faster grasp of concepts. A diagram can serve as a visual roadmap for details covered in the accompanying text.

How to choose a SIG as a non-code Kubernetes contributor

Fri, 09 Jul 2021 00:00:00 +0000

Kubernetes contributors aren’t people in capes or part of some secret society. How to start committing to the GitHub repos that make up the project is well documented , yet it remains intimidating for many.

A few years ago, I spoke at an event and jokingly said, “Kubernetes is just a bunch of APIs and YAML… I’m a contributor; you don’t believe me?” After that talk, someone pulled me aside and asked if I was the Kubernetes contributor. They wanted to get involved in the community. Then came the real question, “I don’t know which special interest group (SIG) I would work in.”

From Kubernetes for work to Kubernetes for play

Tue, 01 Jun 2021 00:00:00 +0000

Addendum by Matt Broberg on May 26, 2021

It's with a heavy heart that this story of Peeyush's contribution begins by acknowledging his sudden passing. Peeyush was a foundational member of the Upstream Marketing subproject. I saw his friendly face every Friday for over a year, and often chat about life before others joined the call. He was kind, incredibly funny, and a loving father. He was also an incredible technologist with years of hands-on experience with Kubernetes, but he spent his time building a space dedicated to communication and connection. He valued making all contributors feel like this community can be their home, and he was incredibly successful at it.

We lost a friend this week. If you're mourning that loss, know you're not alone. Whatever you do to honor him, may it be with as much kindness as he brought to others every day. We have started to collect some of our thoughts and memories of Peeyush as a memorial to him and what he brought to the community. If you would like to share some of your own, please open a PR adding your own memories of him.

My first encounter with Kubernetes was at my first job when a large banking customer wanted to evaluate Kubernetes on ppc64le architecture for application deployment. I was intrigued as it wasn’t every day when a bank seeks to consider something new! That was also my first interaction with Golang and I loved it instantly. I mean, who doesn’t love a cross compiled statically linked binary?! Before that, I was mostly working with Python and OpenStack, which are great as well. But Kubernetes opened a whole new world for me. Being familiar with Docker, which still was pretty new at that time, and the awesome cross-compilation capabilities of Go, I was quickly able to build a proof of concept, and my team loved it.

Announcing the Kubernetes Contributor Stories Series

Fri, 14 May 2021 00:00:00 +0000

The Kubernetes contributor community is vast. We have tens of thousands of members by any conservative estimate and many hundreds involved day-to-day. We are from all around the world, all kinds of backgrounds, all types of expertise, and we are all Kubernetes contributors.

We also have this amazing new website dedicated specifically to Kubernetes contributors. With that in mind, let’s combine the two.

We are asking any and all contributors to share their unique story to highlight the many ways they show up to be part of the Kubernetes community. Here are some

Contributing to the Development Guide

Mon, 28 Sep 2020 00:00:00 +0000

When most people think of contributing to an open source project, I suspect they probably think of contributing code changes, new features, and bug fixes. As a software engineer and a long-time open source user and contributor, that’s certainly what I thought. Although I have written a good quantity of documentation in different workflows, the massive size of the Kubernetes community was a new kind of “client.” I just didn’t know what to expect when Google asked my compatriots and me at Lion’s Way to make much-needed updates to the Kubernetes Development Guide.

Announcing the Contributor Website

Mon, 24 Aug 2020 00:00:00 +0000

Welcome to kubernetes.dev , the Kubernetes Contributor website; built to become the one stop shop for Kubernetes contributor content and news. It brings important documentation scattered throughout the project into one central location.

Resources for contributors

At launch, the contributor site will host a subset of our documentation. Some highlights include (with short links in parenthesis):

Our contributor guide (k8s.dev/guide ) walks you through the first steps to becoming a contributor
The contributor cheatsheet (k8s.dev/cheatsheet ) has common tips and tricks for regular contribution
The community calendar (k8s.dev/calendar ) shows all the upcoming community group meetings
Current release cycle information (k8s.dev/release ) lets you stay up-to-date on upcoming release deadlines and milestones.

TIP: As seen above, the k8s.dev domain can be substituted for kubernetes.dev for easy short-linking :)

Add an nftables-based kube-proxy backend

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

KEP-3866: Add an nftables-based kube-proxy backend

Summary
Motivation
Proposal
- Notes/Constraints/Caveats
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

The default kube-proxy implementation on Linux is currently based on iptables. IPTables was the preferred packet filtering and processing system in the Linux kernel for many years (starting with the 2.4 kernel in 2001). However, problems with iptables led to the development of a successor, nftables, first made available in the 3.13 kernel in 2014, and growing increasingly featureful and usable as a replacement for iptables since then. Development on iptables has mostly stopped, with new features and performance improvements primarily going into nftables instead.

Add AppArmor Support

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

Add AppArmor Support

Release Signoff Checklist
Summary
Motivation
Proposal
- API
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Syncing fields & annotations on workload resources

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add CDI devices to device plugin API

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

KEP-4009: Add CDI devices to device plugin API

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing

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

KEP-4540: Add CPUManager policy option to restrict reservedSystemCPUs to system daemons and interrupt processing

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
  - Story 2
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add generic control plane staging repository(ies)

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

KEP-4080: Add generic control plane staging repository(ies)

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add gRPC probe to Pod.Spec.Container.{Liveness,Readiness,Startup}Probe

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

KEP-2727: Add GRPC Probe

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
- Alpha
- Beta
- GA
Drawbacks
Alternatives
References
Infrastructure Needed (Optional)

Release Signoff Checklist

Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements (not the initial KEP PR)
KEP approvers have approved the KEP status as implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

Add gRPC probe to Pod.Spec.Container.{Liveness,Readiness,Startup}Probe.

Add Informer Metrics

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

KEP-4346: Add Informer Metrics

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add job creation timestamp to job annotations

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

KEP-4026: Add job creation timestamp to job annotations

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add kubelet instance configuration to configure CRI socket for each node

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

Add NonPreempting Option For PriorityClasses

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

Add NonPreempting Option For PriorityClasses

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
- Risks and Mitigations
Design Details
- Testing Plan
- Graduation Criteria
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add pod-startup liveness-probe holdoff for slow-starting pods

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

Add pod-startup liveness-probe holdoff for slow-starting pods

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Implementation History

Release Signoff Checklist

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

Slow starting containers are difficult to address with the current status of health probes: they are either killed before being up, or could be left deadlocked during a very long time before being killed.

Add ProcMount option

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

KEP-4265: add ProcMount option

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add Recreate Update Strategy to StatefulSet

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

KEP-3541: Add Recreate Update Strategy to StatefulSet

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
- Downtime Requirement
- Limited Rollback Options
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add Resource Health Status to the Pod Status for Device Plugin and DRA

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

KEP-4680: Add Resource Health Status to the Pod Status for Device Plugin and DRA

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add support for a kubelet drop-in configuration directory

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

KEP-3983: Add support for a drop-in kubelet configuration directory

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
  - Story 2
  - Story 3
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add support for AdminNetworkPolicy resources

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

KEP-2091: Add support for AdminNetworkPolicy resources

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add user fields to atomic write volumes

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

KEP-5936: Add user fields to atomic write volumes

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Add webhook hosting to CCM.

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

KEP-2699: Add webhook hosting capability to CCM framework

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Adding AppProtocol to Services and Endpoints

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

Adding AppProtocol to Services and Endpoints

Summary
Motivation
- Goals
Proposal
Alpha -> Beta
Beta -> GA
- Test plan
- Production Readiness Review Questionnaire

Summary

Kubernetes does not have a standardized way of representing application protocols. When a protocol is specified, it must be one of TCP, UDP, or SCTP. With the EndpointSlice beta release in 1.17, a concept of AppProtocol was added that would allow application protocols to be specified for each port. This KEP proposes adding support for that same attribute to Services and Endpoints.

Admission Webhook Match Conditions

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

KEP-3716: Admission Webhook Match Conditions

Release Signoff Checklist
Summary
Motivation
Proposal
- API
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Future Work
- Cross-webhook match conditions
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Aggregated Discovery

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

KEP-3352: Aggregated Discovery

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Notes/Constraints/Caveats (Optional)
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Allow a Network Policy to contemplate a set of ports in a single rule

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

Summary

Today the ports field in ingress and egress network policies is an array that needs a declaration of each single port to be contemplated. This KEP proposes to add a new field that allows a declaration of a port range, simplifying the creation of rules with multiple ports.

Allow bind mount options (noexec, nodev, nosuid) on volumeMounts

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

KEP-5855: Allow bind mount options (noexec, nodev, nosuid) on volumeMounts

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Allow DaemonSets to surge during update like Deployments

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

Allow DaemonSets to surge during update like Deployments

Summary
Motivation
- Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History

Summary

Daemonsets allow two update strategies - OnDelete which only replaces pods when they are deleted and RollingUpdate which supports MinAvailable like Deployments but not Surge. Daemonsets should support Surge in order to minimize DaemonSet downtime on nodes. This will allow daemonset workloads to implement zero-downtime upgrades.

Allow HostNetwork Pods to Use User Namespaces

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

KEP-5607: Allow HostNetwork Pods to Use User Namespaces

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Allow informers for getting a stream of data instead of chunking

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

KEP-3157: allow informers for getting a stream of data instead of chunking.

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Appendix
- Sources of LIST request
- Steps followed by informers
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Allow Replacement of Pods in a Job when fully terminating

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

KEP-3939: Allow replacement of Pods in a Job when fully terminated

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Allow special characters environment variable

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

KEP-4369: Allow special characters in environment variables

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Allow zero value for Sleep Action of PreStop Hook

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

KEP-4818: Allow zero value for Sleep Action of PreStop Hook

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Allows setting arbitrary FQDN as the pod's hostname

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

KEP-4762: Allows setting arbitrary FQDN as the pod’s hostname

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Anago to Krel Migration

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

Anago to Krel Migration

Objectives
Milestones
- First Milestone: Complete the Migration Effort
  - Open Issues
  - Acceptance Criteria
- Second Milestone: Introduce krel stage/release
  - Open Issues
Risks
Quality/Test Plan

Moving away from running bash in production in k/release

Objectives

This roadmap defines a strategy for achieving two primary goals: migrating exchangeable bits of bash code within anago to krel and creating a Golang native replacement for anago.

API gzip compression support

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

Graduate API gzip compression to GA

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
Implementation History

Summary

Kubernetes sometimes returns extremely large responses to clients outside of its local network, resulting in long delays for components that integrate with the cluster in the list/watch controller pattern. Kubernetes should properly support transparent gzip response encoding, while ensuring that the performance of the cluster does not regress for small requests.

API Server Authentication to Admission Webhooks

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

KEP-6060: API Server Authentication to Admission Webhooks

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Terms
Proposal
- Sequence Diagrams
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

API Server Network Proxy

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

Summary

We will build an extensible system which controls network traffic from the Kube API Server. We will add a traffic egress or network proxy system. The KAS can be configured to send traffic (or not) to one or more of the proxies. Users can drop in custom proxies if the default behavior is insufficient.

APIServer Tracing

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

KEP-647: APIServer Tracing

Release Signoff Checklist
Summary
Motivation
Proposal
- User Stories
  - Steady-State trace collection
  - On-Demand trace collection
- Risks and Mitigations
Design Details
Graduation requirements
- Upgrade / Downgrade Strategy
- Version Skew Strategy
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives considered
- Introducing a new EgressSelector type
- Other OpenTelemetry Exporters

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Apply

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

Apply

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Implementation Details/Notes/Constraints [optional]
Production Readiness Review Questionnaire
Graduation Criteria
- Upgrade / Downgrade Strategy
Implementation History
Drawbacks
Alternatives

Summary

kubectl apply is a core part of the Kubernetes config workflow, but it is buggy and hard to fix. This functionality will be regularized and moved to the control plane.

Appropriate use of node-role labels

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

Appropriate use of node-role labels

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
- Use of node-role.kubernetes.io/* labels
- Current users of node-role.kubernetes.io/* within the project that must change
Design Details
Production Readiness Review Questionnaire
Implementation History
Future work
Reference

Release Signoff Checklist

ACTION REQUIRED: In order to merge code into a release, there must be an issue in kubernetes/enhancements referencing this KEP and targeting a release milestone before Enhancement Freeze of the targeted release.

Artifact Distribution Policy

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

KEP 3000: Image Promotion and Distribution Policy

Summary
Why a new domain?
How can we help?
Proposal
What exactly are you doing?
Alternatives / Background
- How much is this going to save us?

Summary

For a few years now, we have been using k8s.gcr.io in all our repositories as default repository for downloading images from.

Artifact Generation

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

Asynchronous API calls during scheduling

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

KEP-5229: Asynchronous API calls during scheduling

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Asynchronous Preemption

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

KEP-4832: Asynchronous Preemption

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
  - When kube-apiserver is unstable
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Introduce a new extension point

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Authorize with Selectors

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

KEP-4601: Authorize with Selectors

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Auto delete PVCs created by StatefulSet

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

KEP-1847: Auto delete PVCs created by StatefulSet

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Auto-refreshing official CVE feed

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

KEP-3203: Auto-Refreshing Official CVE Feed

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
- User Stories (Optional)
  - Story 1
  - Story 2
  - Story 3
- Story 4
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Storage of CVE feed blob
  - 1. Only use Google Cloud Bucket
  - 2. Only use Git Repository
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release .

Azure Availability Zones

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

Backoff Limits Per Index For Indexed Jobs

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

KEP-3850: Backoff Limits Per Index For Indexed Jobs

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Beta APIs Are Off by Default

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

KEP-3136: Beta APIs Are Off by Default

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Beta Feature Gate Promotion Requirements

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

KEP-5241: Beta Feature Gate Promotion Requirements

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
  - What if I need to add capability to my feature?
  - Who will make sure that new KEPs follow the promotion rules?
- Graduation Criteria
Drawbacks
- This may slow the rate that new features are promoted.
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Block ExternalIPs via Admission Control

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

KEP-2200: Deny use of ExternalIPs via admission control

Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

This proposal is in response to CVE-2020-8554: “Man in the middle using LoadBalancer or ExternalIPs”.

bound service account token improvements

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

KEP-4193: bound service account token improvements

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Bound Service Account Tokens

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

Bound Service Account Tokens

Summary
Background
Motivation
Design Details
Production Readiness Review Questionnaire

Summary

This KEP describes an API that would allow workloads running on Kubernetes to request JSON Web Tokens that are audience, time and eventually key bound. In addition, this KEP introduces a new mechanism of distribution with support for bound service account tokens and explores how to migrate from the existing mechanism backwards compatibly.

Bounding Self-Labeling Kubelets

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

Bounding Self-Labeling Kubelets

Motivation
- Capturing Dedicated Workloads
Proposal
Implementation Timeline
Alternatives Considered

Motivation

Today the node client has total authority over its own Node labels. This ability is incredibly useful for the node auto-registration flow. The kubelet reports a set of well-known labels, as well as additional labels specified on the command line with --node-labels.

Breaking apart the Kubernetes test tarball

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

Breaking apart the kubernetes test tarball

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
References
Implementation History

Release Signoff Checklist

k/enhancements issue in release milestone and linked to KEP
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

The Kubernetes release artifacts include a “mondo” test tarball which includes both “portable” test sources (such as shell scripts and image manifests) as well as platform-specific test binaries for all supported client, node, and server platforms.

Building a Dockerless Kubelet

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

Building a Dockerless Kubelet

Release Signoff Checklist
Summary
Motivation
- History
Returning to Motivation
- Goals
- Non-Goals
Proposal
Design Details
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

This proposal outlines a plan to enable building a dockerless Kubelet. We define a dockerless Kubelet as a Kubelet with no “Docker-specific” code and no dependency on the docker/docker Golang package. We define “Docker-specific” code as code which only serves a purpose when Docker is the container runtime. “Docker-specific” code is never executed when the Kubelet uses a remote container runtime (i.e. containerd or CRI-O).

Building Kubernetes Without In-Tree Cloud Providers

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

Building Kubernetes Without In-Tree Cloud Providers

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Implementation History
Drawbacks [optional]
Alternatives [optional]
Infrastructure Needed [optional]

Release Signoff Checklist

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

This proposal outlines a plan to enable building Kubernetes without the in-tree cloud providers in preparation for removing them entirely .

Built-in declarative defaults

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

KEP-1929: Built-in declarative defaults

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
- Test Plan
- Graduation Criteria
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

cAdvisor-less, CRI-full Container and Pod Stats

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

cAdvisor-less, CRI-full Container and Pod Stats

cAdvisor-less, CRI-full Container and Pod Stats

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Calendar and Meeting Guidelines

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

Project meetings are a life line of the Kubernetes project. Consistent calendaring is a challenge with many different clients, corporate policies, time zones and various iterations of Daylight Savings Time. This guide should help you navigate some of the common pitfalls and provide some tips & best practices.

Please feel free to PR in your favorite tips and tricks that may help others.

Calendar Guidelines

Establishing a New Meeting

“I’m a chair for a SIG or WG and need to set up a meeting.”

CBOR Serializer

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

KEP-4222: CBOR Serializer

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CEL for Admission Control

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

KEP-3488: CEL for Admission Control

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Background
Considerations
Proposal
Design Details
GA
- Upgrade / Downgrade Strategy
- Version Skew Strategy
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Future Work
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CEL for CRD AdditionalPrinterColumns

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

KEP-4595: CEL for CRD AdditionalPrinterColumns

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Certificates API

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

Certificates API

Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Graduation Criteria
- Beta to GA Graduation
Implementation History

Summary

The Certificates API enables automation of x509 credential provisioning by providing a programmatic interface for clients of the Kubernetes API to request and obtain x509 certificates from a Certificate Authority (CA).

Certificates copy for join --control-plane

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

cgroups v2

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

Cgroups v2

Summary
Motivation
Goals
Non-Goals
User Stories
Implementation Details
Design
Production Readiness Review Questionnaire
Proposal
- Dependencies on OCI and container runtimes
- Current status of dependencies
Current cgroups usage and the equivalent in cgroups v2
Risk and Mitigations

Summary

A proposal to add support for cgroups v2 to kubernetes.

Clarify if/how controllers can use status to track non-observable state

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

KEP-2527: Clarify if/how controllers can use status to track non-observable state

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Alternative 1: Add a new top-level stanza to spec/status resources
  - Examples
  - Tradeoffs
- Alternative 2: Sub-divide spec
  - Examples
  - Tradeoffs
  - Notes

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Cleaning up container streaming requests

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

Cleaning up container streaming requests

Release Signoff Checklist
Summary
Background
Motivation
- Goals
- Non-Goals
Proposal
- Rollout Plan
- Risks and Mitigations
  - Dependence on apiserver redirects
  - Rollout breakage
Design Details
Implementation History

Release Signoff Checklist

Cleaning up IPTables Chain Ownership

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

KEP-3178: Cleaning up IPTables Chain Ownership

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Notes/Constraints/Caveats
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

Kubelet currently creates some IPTables chains at startup. In the past it actually used some of them, but with the removal of dockershim it no longer does. Additionally, for historical reasons, it creates some IPTables chains that are duplicates of chains also created by kube-proxy, and some that are only used by kube-proxy, but which kube-proxy requires kubelet to create on its behalf. (The initial comment in kubernetes #82125 has more details on the history of how we got to where we are now, or at least to where we were before dockershim was removed.)

Client Executable Proxy

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

KEP-2718: Client Executable Proxy

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Alternative Proposal: Request Replacement

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Client Opt-out for managedFields in API Response

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

KEP-5958: Client Opt-out for managedFields in API Response

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
  - Story 2
- Risks and Mitigations
Design Details
Production Readiness Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Client-go Apply

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

KEP-2155: Apply for client-go’s typed client

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
  - Poor adoption
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Cloud Dual-Stack --node-ip Handling

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

KEP-3705: Cloud Dual-Stack –node-ip Handling

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

Kubelet supports dual-stack --node-ip values for clusters with no cloud provider (eg, “bare metal” clusters), but not for clusters using a cloud provider. This KEP proposes to fix that.

Cloud Provider Documentation

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

Documentation Requirements for Kubernetes Cloud Providers

Summary
Motivation
- Goals
- Non-Goals
Proposal
Implementation Details/Notes/Constraints [optional]
Risks and Mitigations
Graduation Criteria
Alternatives [optional]
Implementation History

Summary

This KEP describes the documentation requirements for both in-tree and out-of-tree cloud providers. These requirements are meant to ensure the usage and integration of cloud providers with the rest of the Kubernetes ecosystem is concise and clear and that documentation layout across providers is consistent.

Cloud Provider for BaiduCloud

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

Cloud Provider For HUAWEI CLOUD

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

Cluster Profile API

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

KEP-4322: ClusterProfile API

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
API Example
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Cluster Trust Bundles

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

KEP-3257: Cluster Trust Bundles

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Trust Anchor Distribution for Private CAs
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

ClusterID for ClusterSet Identification

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

KEP-2149: ClusterId for ClusterSet identification

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

ClusterProfile credentials plugin

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

KEP-5339: Plugin for Credentials in ClusterProfile

Status

This KEP has been replaced by KEP-4322: ClusterProfile API . The credential provider plugin mechanism, accessProviders API field, and related design details have been merged into KEP-4322.

Code Of Conduct

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

CNCF Community Code of Conduct v1.3

Other languages available:

Community Code of Conduct

Code Of Conduct

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

Kubernetes follows the CNCF Code of Conduct .

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the Kubernetes Code of Conduct Committee via conduct@kubernetes.io .

Code of Conduct Charter

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

Mission/Purpose

Our primary mission is creating and maintaining a safe and respectful community. Our role is to provide and enforce a well-considered viewpoint on what constitutes acceptable behavior within our community. The Code of Conduct serves as the primary policy document and is supported with additional references and tools as needed. Since maintaining a safe environment is a very large part of what the committee does, we must carefully balance transparency of process with preserving the privacy of all individuals involved when an incident report is made to this committee or to any other community leader.

Community Survey Requests

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

What’s a Community Survey?
Survey Request Process
Tips and Notes Around Surveys

Let us help you make your survey a success.

The Kubernetes project has access to the CNCF SurveyMonkey account for creating community surveys, and SIG-Contributor Experience includes people who can give advice on improving the quality of surveys, as well as promote them. As such, what follows is the process for requesting such a community survey, in order to maximize its reach and data quality.

Comparable Resource Version

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

KEP-5504: Comparable Resource Versions

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Compatibility Versions

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

KEP-4330: Compatibility Versions in Kubernetes

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Component Flagz

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

KEP-4828: Component Flagz

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - User Story 1: Debugging Component Behavior
  - User Story 2: Verifying Flag Changes
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Component Statusz

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

KEP-4827: Component Statusz

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CompositePodGroup API

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

KEP-6012: CompositePodGroup API

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Concurrent Watch Object Decode

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

KEP-6178: Concurrent Watch Object Decode

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Scale the pool with GOMAXPROCS
- Make the pool size configurable

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Conditional Authorization

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

KEP-5681: Conditional Authorization

Author: Lucas Käldström, Upbound
Contributor: Micah Hausler, AWS

Release Signoff Checklist
Abstract
Background and Major Considered Alternatives
Proposal
Other Kubernetes authorization enforcement points, with and without conditions-awareness
Authorizer requirements
Production Readiness Review Questionnaire
TODOs
Alternatives Considered
Drawbacks
Appendix A: Further resources
Appendix B: Future addition sketch: Conditional Reads

Release Signoff Checklist

Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements (not the initial KEP PR)
KEP approvers have approved the KEP status as implementable
Design details are appropriately documented
(R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
- e2e Tests for all Beta API Operations (endpoints)
- (R) Ensure GA e2e tests meet requirements for Conformance Tests
- (R) Minimum Two Week Window for GA e2e tests to prove flake free. Not yet applicable for this KEP
(R) Graduation criteria is in place
- all GA Endpoints must be hit by Conformance Tests within one minor version of promotion to GA. Not yet applicable for this KEP
Production readiness review completed
Production readiness review approved
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Abstract

This KEP proposes extending Kubernetes authorization to support conditions, where an authorization decision depends on resource data (labels and fields of object), rather than only metadata (apiGroup, resource, namespace, name). This enables more fine-grained, and most importantly, cohesive access control policies that span both authorization and admission phases, while maintaining backward compatibility with existing authorizers.

Configurable Pod DNS

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

Configurable Pod DNS

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
Implementation History

Summary

This proposal gives users a way to overlay tweaks into the existing DnsPolicy. A new PodSpec field dnsConfig will contains fields that are merged with the settings currently selected with DnsPolicy.

Configurable scale up/down velocity for HPA

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

Configurable scale up/down velocity for HPA

Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
- Implementation Details/Notes/Constraints
Design Details
- Test Plan
- Graduation Criteria

Summary

Horizontal Pod Autoscaler (HPA) automatically scales the number of pods in any resource which supports the scale subresource based on observed CPU utilization (or, with custom metrics support, on some other application-provided metrics). This proposal adds scale velocity configuration parameters to the HPA to control the rate of scaling in both directions.

Configurable Scaling Delay with Pod Resource Exposure

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

KEP-6122: Configurable Scaling Delay with Pod Resource Exposure

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Use Cases
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Configurable tolerance for HPA

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

KEP-4951: Configurable tolerance for HPA

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Configure FQDN as Hostname for Pods

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

KEP-1797: Configure FQDN as Hostname for Pods

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Configure the max CrashLoopBackOff delay

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

KEP-5593: Configure the max CrashLoopBackOff delay

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Appendix A
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Consider Terminating Pods in Deployments

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

KEP-3973: Consider Terminating Pods in Deployments

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Consistent Reads from Cache

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

Consistent Reads from Cache

Kubernetes Get and List requests are guaranteed to be “consistent reads” if the resourceVersion parameter is not provided. Consistent reads are served from etcd using a “quorum read”.

But often the watch cache contains sufficiently up-to-date data to serve the read request, and could serve it far more efficiently.

This KEP proposes a mechanism to serve most reads from the watch cache while still providing the same consistency guarantees as serving the read from etcd.

consistent-resource-version-semantics

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

Consistent Resource Version Semantics for List

Summary
Motivation
- Goals
Proposal
Alternatives Considered
- Alternative: Introduce ExactResourceVersion and MinResourceVersion parameters
- Alternative: Use syntax in the query string
Implementation History

Summary

Make resource version semantics consistent for list requests regardless of pagination.

Consolidate Workload controllers life cycle status

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

KEP-2804: Consolidate Workload controllers life cycle status

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Constrained Impersonation

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

KEP-5284: Constrained Impersonation

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Container Resource based Autoscaling

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

KEP-1610: Container Resource based Autoscaling

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Container Restart Policy

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

KEP-5307: Container Restart Rules

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Wrapping entrypoint
- Non-declarative (callbacks based) restart policy
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Container Stop Signals

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

KEP-4960: Container Stop Signals

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Context support in k8s.io/client-go

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

Context support in k8s.io/client-go

Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Alternatives

Summary

This proposal outlines a refactoring that would allow propagating of context with client-go with API calls made using k8s.io/client-go clientsets.

Motivation

When using client-go, external calls to the Kubernetes API are made in order to manage resources. Adding support for context propagation along these request paths enables clean and efficient implementation of cross cutting functionality. This functionality initially will include:

Contextual logging

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

KEP-3077 : contextual logging

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
  - Story 2
  - Story 3
  - Story 4
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Status and next steps
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Continuously Deploy K8s Prow

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

KEP-2539: Continuously Deploy K8s Prow

Release Signoff Checklist
Summary
Motivation
- Goals
  - Prow Users
  - Prow Oncall
- Non-Goals
Proposal
- Notes/Constraints/Caveats (Optional)
  - Breaking Changes in Prow
Design Details
Implementation History
Alternatives
- A new tool merges autobump PRs
  - Pros:
  - Cons:

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Contributor Site

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

Contributor Site

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Graduation Criteria
Implementation History
Drawbacks
Alternatives

Summary

We need a way to organize and publish information targeted at contributors. In order to continue to scale the Kubernetes contributor community we need a convenient, scalable and findable way to publish information.

Motivation

While the current kubernetes.io site is great for end users, it isn’t often used by or aimed at project contributors. Instead, most contributors look at documentation in markdown files that are spread throughout a wide set of repos and orgs. It is difficult for users to find this documentation.

Controller Manager Leader Migration

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

Controller Manager Leader Migration

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Notes/Constraints/Caveats (Optional)
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Coordinated Leader Election

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

KEP-4355: Coordinated Leader Election

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Future Work
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CPU Manager

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

CPU Manager

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Proposed and not implemented items
  - Policy 3: "dynamic" cpuset control
    - Implementation sketch
Infrastructure Needed (Optional)
Appendixes

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CPUManager policy option to align CPUs by Socket instead of by NUMA node

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

KEP-3327: Add CPUManager policy option to align CPUs by Socket instead of by NUMA node

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CPUManager Policy Option to Distribute CPUs Across NUMA Nodes Instead of Packing Them

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

KEP-2902: Add CPUManager policy option to distribute CPUs across NUMA nodes instead of packing them

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CRD Validation Expression Language

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

KEP-2876: CRD Validation Expression Language

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Graduation Criteria
- Beta
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CRD Validation Ratcheting

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

KEP-4008: CRD Validation Ratcheting

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Test Plan - Prerequisite testing updates - Unit tests - Integration tests - e2e tests
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Create a `k8s.io/component-base` repo

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

CRI Container Log Rotation

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

KEP-2411: CRI Container Log Rotation

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CRI List Streaming

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

KEP-5825: CRI List Streaming

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
References
- Standards and Documentation
- Related Issues and PRs

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CronJobs (previously ScheduledJobs)

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

KEP-19: CronJobs (previously ScheduledJobs)

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
API changes
Tests
Implementation plan
Graduation Criteria
Production Readiness Review Questionnaire
Implementation History
Alternatives and Further Reading
- Cron Aspect
Improvements/Considerations

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Cross resource group nodes

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

CSI driver opt-in for service account tokens via secrets field

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

KEP-5538: CSI driver opt-in for service account tokens via secrets field

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CSI Pod Info on Mount

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

CSI Pod Info on Mount

Summary
Test Plan
Graduation Criteria
- Alpha to Beta
- Beta to GA
Implementation History

Summary

This document presents a design to allow Kubernetes to pass metadata such as Pod name and namespace to the CSI NodePublishVolume call if a CSI driver requires it.

The detailed design was originally implemented as a design proposal .

CSI Raw Block Volumes

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

CSI Raw Block Volumes

Summary
Motivation
- Goals
- Non-Goals
Proposal
Upgrade/Downgrade Strategy
Test Plan
- Unit tests
- E2E tests
Graduation Criteria
- Alpha -> Beta
- Beta -> GA
Implementation History

Summary

Raw block support has been added to both the core of Kubernetes (including API support and support in kubelet for a subset of volume types) as well as the CSI specification. This feature is specifically to add raw block support to kubelet for volumes of the “csi” type by taking advantage of the now-standardized CSI RPCs.

CSI Sidecars All in one

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

KEP-4958: CSI Sidecars All In One

Release Signoff Checklist
Summary
Motivation
Proposal
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- ReleaseManagement
- ReproducibleBuilds
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CSI Snapshot

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

KEP-177: CSI Snapshot

Release Signoff Checklist
Summary
Test Plan
- Unit tests
- E2E tests
Graduation Criteria
- Alpha->Beta
- Beta->GA
Snapshot Beta
Snapshot GA
- Changes Implemented
- Additional Changes Planned
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CSI Snapshot Webhook

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

KEP-1900: Add additional validation to volume snapshot objects

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CSI Volume Topology

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

CSI Volume Topology

Summary
Upgrade/Downgrade Strategy
- Deprecations
Version Skew Strategy
Test Plan
- GA testing
Graduation Criteria
- Alpha->Beta
- Beta->GA
Implementation History

Summary

This KEP is written after the original design doc has been approved and implemented. Design for CSI Volume Topology Support in Kubernetes is incorporated as part of the CSI Volume Plugins in Kubernetes Design Doc .

CSR Duration

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

KEP-2784: CSR Duration

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Custom profiling support in kubectl debug command

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

KEP-4292: Custom profiling support in kubectl debug command

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Flags for all fields
- Customizable Pod Spec instead corev1.Container

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Custom Resource Field Selectors

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

KEP-4358: Custom Resource Field Selectors

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
- Test Plan
- Graduation Criteria
  - Alpha
  - Beta
GA
- Upgrade / Downgrade Strategy
- Version Skew Strategy
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- OpenAPI Discovery
  - Declare selectable fields to the fieldSelector path parameter of OpenAPI
  - Declare selectable fields by annotating schema fields as being selectable, e.g.:
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

CustomResourceDefinition Conversion Webhook

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

CustomResourceDefinition Conversion Webhook

Summary
Definitions
Motivation
- Goals
- Non-Goals
Proposal
Detailed Design
Examples
- Example of Writing Conversion Webhook
Example of Updating CRD from one to two versions
- Risks and Mitigations
Graduation Criteria
Implementation History
Alternatives

Summary

This document proposes a detailed plan for adding support for version-conversion of Kubernetes resources defined via Custom Resource Definitions (CRD). The API Server is extended to call out to a webhook at appropriate parts of the handler stack for CRDs.

Declarative API Definitions

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

KEP-5975: Declarative API Definitions

Summary
Motivation
Proposal
Examples
- Adding a New API Resource
- Adding a New Field to an Existing API
Design Details
Production Readiness Review Questionnaire
Alternatives
Future Work
Implementation History

Note: This KEP tracks an internal code organization change that is not visible to end users. There are no feature gates and no alpha/beta/stable transitions. We are using the KEP process to encourage discussion and community involvement.

Declarative Validation

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

KEP-4153: Declarative Validation of Kubernetes Native Types

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Analysis of existing validation rules
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Validate On Storage Type Rather than Request Type
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Declarative Validation

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

KEP-5073: Declarative Validation of Kubernetes Native Types With validation-gen

Release Signoff Checklist
Summary
Motivation
Proposal
Rollout Strategy(Timeline)
Lifecycle: Promotion Process (Continuous)
Analysis of existing validation rules
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Use CEL and OpenAPI libraries directly for K8s Native Types (KEP-4153)
Infrastructure Needed (Optional)
Future Work
- "New K8s Native APIs" Design Partner For Declarative Validation in 1.34

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Decouple PodGroup API

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

KEP-5832: Decouple PodGroup from Workload API

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Embedded PodGroups (Status Quo)
- Support both embedded and standalone PodGroup
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Decouple TaintManager from NodeLifeCycleController

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

KEP-3902: Decouple Taint-based Pod Eviction from Node Lifecycle Controller

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)
Note

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Default Pod Topology Spread

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

Default Pod Topology Spread

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

With Pod Topology Spread , workload authors can define spreading rules for their loads based on the topology of the clusters. The spreading rules are defined in the PodSpec, thus they are tied to the pod.

Defaulting for Custom Resources

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

Defaulting for Custom Resources

Summary
Motivation
- Goals
- Non-Goals
Proposal
References
Alternatives considered
Implementation History

Summary

Defaulting is a fundamental step in the processing of API objects in the request pipeline of the kube-apiserver. Defaulting happens during deserialization, i.e. after decoding of a versioned object, but before conversion to a hub type.

Defend against accidental credential logging via static analysis interation into Prow.

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

KEP-1933: Defend Against Logging Secrets via Static Analysis

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Notes/Constraints/Caveats
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Defining the Kubernetes Release Cadence

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

KEP-2572: Defining the Kubernetes Release Cadence

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
- Risks and Mitigations
Design Details
- Schedule Policy
- Feedback survey
Implementation History
- GitHub Discussion
- Leads meeting feedback session
Drawbacks
Alternatives

Release Signoff Checklist

(R) Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements (not the initial KEP PR)
(R) KEP approvers have approved the KEP status as implementable
(R) Design details are appropriately documented
(R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
(R) Graduation criteria is in place
(R) Production readiness review completed
(R) Production readiness review approved
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

With this KEP, SIG Release proposes to change the current Kubernetes release cadence from 4 down to 3 releases per year. This cadence started in ad hoc manner in 2020 due to the ongoing COVID-19 pandemic. This KEP serves to formalize this release cadence, which will shape the development of the release calendars for the Kubernetes 1.22 and 1.23 releases, each of which will be 15 weeks in duration.

Deployment Pod Replacement Policy

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

KEP-5882: Deployment Pod Replacement Policy

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Deprecate & remove Kubelet RunOnce mode

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

KEP-4580: Deprecate & remove Kubelet RunOnce mode

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Deprecate and remove SelfLink

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

KEP-1164: Deprecate and Remove SelfLink

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Deprecate ipvs mode in kube-proxy

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

KEP-5495: Deprecate IPVS mode in kube-proxy

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Summary

This KEP proposes deprecation of ipvs in kube-proxy.

Deprecate klog specific flags in Kubernetes components

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

KEP-2845: Deprecate klog specific flags in Kubernetes Components

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
- Test Plan
- Graduation Criteria
  - Alpha
  - Beta
  - GA
Implementation History
Drawbacks
Alternatives
Production Readiness Review Questionnaire

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Deprecate Service.spec.externalIPs

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

KEP-5707: Deprecate Service.spec.externalIPs

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Keep externalIPs with Enhanced Security

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Deprecate status.nodeInfo.kubeProxyVersion field

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

KEP-4004: Deprecate the kubeProxyVersion field of v1.Node

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

Deprecate the status.nodeInfo.kubeProxyVersion field of v1.Node

Deprecate v1.Endpoints and Associated Controllers

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

KEP-4974: Deprecate v1.Endpoints and Associated Controllers

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Device Plugins

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

KEP-3573: Device Plugins

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
References
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Different protocols in the same service definition with type=loadbalancer

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

KEP-1435: different protocols in the same service definition with type=loadbalancer

Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Summary

This feature enables the creation of a LoadBalancer Service that has different port definitions with different protocols.

Disable AcceleratorUsage Metrics

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

Disable AcceleratorUsage Metrics

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

(R) Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements
(R) KEP approvers have approved the KEP status as implementable
(R) Design details are appropriately documented
(R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
(R) Graduation criteria is in place
(R) Production readiness review completed
Production readiness review approved
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

This KEP outlines the process to deprecate the Accelerator Metrics collected by Kubelet.

Disable cAdvisor json Metrics

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

Disable CAdvisor Json Metrics

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

(R) Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements
(R) KEP approvers have approved the KEP status as implementable
(R) Design details are appropriately documented
(R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
(R) Graduation criteria is in place
(R) Production readiness review completed
Production readiness review approved
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

This KEP outlines the process to deprecate cAdvisor json metrics collected by Kubelet.

Discover cgroup driver from CRI

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

KEP-4033 : Discover cgroup driver from CRI

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Discuss Forum Guidelines

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

Code of conduct
Privacy Policy
Admins
General communication guidelines
- PM (Private Message) conversations
- Escalating and/or reporting a problem
Moderation
- Moderator expectations and guidelines
- Other moderator responsibilities
  - Ingest queue
New category requests

Discuss (discuss.kubernetes.io), is the Kubernetes community forum backed by the Discourse discussion platform. It serves as the primary communication platform for Kubernetes users; replacing the kubernetes-users mailing list in September 2018.

Downward API HugePages

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

KEP-1967: Downward API HugePages

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Admin Access

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

KEP-5018 : DRA: AdminAccess for ResourceClaims and ResourceClaimTemplates

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Consumable Capacity

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

KEP-5075: DRA Consumable Capacity

Release Signoff Checklist
Summary
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
  - Story 2
  - Story 3
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Derived Attributes

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

KEP-6080: DRA Derived Attributes

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Future Considerations
- Derived Attributes in Device Selectors

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Device Attributes Downward API

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

KEP-5304: DRA Device Attributes Downward API

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Device Binding Conditions

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

KEP-5007 : DRA: Device Binding Conditions

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Device Compatibility Groups

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

KEP-5963: DRA Device Compatibility Groups

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Current Workaround: Driver-level Preparation Failure
- Inverted naming: mutualExclusionGroups
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Extended Resource

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

KEP-5004 : DRA: Handle extended resource requests via DRA Driver

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Node Allocatable Resources

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

KEP-5517: DRA: Node Allocatable Resources

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Optional Node Preparation

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

KEP-5945: DRA Optional Node Preparation

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Deploying controller-managed resources without node-local drivers
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Partitionable Devices

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

KEP-4815 : DRA: Add support for partitionable devices

Release Signoff Checklist
Summary
Motivation
Proposal
- Risks and Mitigations
  - Partial scheduling of pods for multi-host devices
  - Validation moved from admission to runtime
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Prioritized List

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

KEP-4816 : DRA: Prioritized Alternatives in Device Requests

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Higher Level Indirection
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Resource Availability Visibility

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

KEP-5677: DRA Resource Availability Visibility

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA ResourceSlice Mixins

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

KEP-5234: DRA: ResourceSlice Mixins

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA Shared Consumable Capacity

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

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

(R) Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements (not the initial KEP PR)
(R) KEP approvers have approved the KEP status as implementable
(R) Design details are appropriately documented
(R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
- e2e tests for all Beta API operations (endpoints)
- (R) Ensure GA e2e tests meet requirements for Conformance Tests
- (R) Minimum two week window for GA e2e tests to prove flake free
(R) Graduation criteria is in place
- (R) all GA endpoints must be hit by Conformance Tests within one minor version of promotion to GA
(R) Production readiness review completed
(R) Production readiness review approved
Implementation history section is up to date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation, such as design docs, SIG meeting notes, relevant PRs/issues, release notes

Summary

Dynamic Resource Allocation (DRA) currently supports:

DRA Structured Parameters

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

KEP-4381 : Dynamic Resource Allocation with Structured Parameters

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA: admin-controlled device attributes

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

KEP-5027 : DRA: admin-controlled device attributes

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Notes/Constraints/Caveats
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Admin-intent in ResourceSlice
- Storing result of patching in ResourceSlice

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA: ClusterResourceClaimTemplate

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

KEP-5978: DRA: ClusterResourceClaimTemplate

NOTE: This KEP was withdrawn in favor of the Out-of-Tree Synchronization Controller alternative .

DRA: device taints and tolerations

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

KEP-5055 : DRA: device taints and tolerations

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA: List Types for Attributes

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

KEP-5491: DRA: List Types for Attributes

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA: ResourceClaim Support for Workloads

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

KEP-5729: DRA: ResourceClaim Support for Workloads

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Increase the size limit on the status.reservedFor field
- Allow ResourceClaims to be reserved for any object

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

DRA: Standard numaNode Device Attribute

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

KEP-6072: DRA: Standard `numaNode` Device Attribute

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Dry-run

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

Kubernetes Dry-run

Dry-run is a new feature that we intend to implement in the api-server. The goal is to be able to send requests to modifying endpoints, and see if the request would have succeeded (admission chain, validation, merge conflicts, …) and/or what would have happened without having it actually happen. The response body for the request should be as close as possible to a non dry-run response.

Release Signoff Checklist
Test Plan
Graduation Criteria
- Beta -> GA Graduation
- Removing a deprecated flag
Specifying dry-run
Admission controllers
Generated values
Storage
kubectl

Release Signoff Checklist

Check these off as they are completed for the Release Team to track. These checklist items must be updated for the enhancement to be released.

DSR and Overlay support in Windows kube-proxy

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

KEP-5100: [RETROACTIVE] DSR and Overlay support in Windows kube-proxy

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Dual Stack API Server

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

KEP-2438: Dual-Stack API Server

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Dynamic Cardinality Enforcement

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

KEP-2305: Dynamic Cardinality Enforcement

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Dynamic Resize of Memory-Backed Volumes

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

KEP-6030: Dynamic Resize of Memory-Backed Volumes

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
  - Story 2
- Risks and Mitigations
  - OOM-kills
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

dynamic resource allocation

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

KEP-3063 : Dynamic Resource Allocation with Control Plane Controller

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Network-attached accelerator
  - Combined setup of different hardware functions
- Notes/Constraints/Caveats
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Efficient Node Heartbeat

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

Efficient Node Heartbeats

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
- Testing Plan
Graduation Criteria
Implementation History
Alternatives

Summary

Node heartbeats are necessary for correct functioning of Kubernetes cluster. This proposal makes them significantly cheaper from both scalability and performance perspective.

Efficient watch resumption after kube-apiserver reboot

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

KEP-1904: Efficient watch resumption after kube-apiserver reboot

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Future work
Alternatives
- Initialize watch cache from etcd history window

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Elastic Indexed Job

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

KEP-3715: Elastic Indexed Job

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Eliminating Internal API Types

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

KEP-6164: Eliminating Internal API Types

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

EmptyDir Volume Permission Mode

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

KEP-5502: EmptyDir Volume Permission Mode

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1: Restricted Directory Permissions
  - Story 2: Shared Temporary Storage with Sticky Bit
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Alternative 1: Boolean stickyBit field
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Enable per-request Read/Write Deadline

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

KEP-4460: Enable per-request Read/Write Deadline

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Enable Writable Cgroups

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

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

EndpointSlice API

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

KEP-0752 EndpointSlices

Summary
Motivation
- Goals
- Non-Goals
Proposal
Estimation
Sample Case 1: 20,000 endpoints, 5,000 nodes
Sample Case 2: 20 endpoints, 10 nodes
Implementation
Roll Out Plan
Graduation Criteria
Production Readiness Review Questionnaire
Implementation History
Alternatives
FAQ

Summary

This KEP was converted from the original proposal doc . The current Core/V1 Endpoints API comes with severe performance/scalability drawbacks affecting multiple components in the control-plane (apiserver, etcd, endpoints-controller, kube-proxy). This doc proposes a new EndpointSlice API aiming to replace Core/V1 Endpoints API for most internal consumers, including kube-proxy. The new EndpointSlice API aims to address existing problems as well as leaving room for future extension.

Enhance HPA Metrics Specificity

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

Enhance HPA Metrics Specificity

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Graduation Criteria
Implementation History
Alternatives

Summary

The External metric source type in the HPA currently supports passing a metric label selectors, which is passed to the custom metrics API (custom.metrics.k8s.io) to select a more specific metrics series. This allows users to more easily make use of existing metrics structure, without need to manipulate their metrics labeling and ingestion externally.

Enhanced NodeIPAM to support Discontiguous Cluster CIDR

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

KEP-2593: Enhanced NodeIPAM to support Discontiguous Cluster CIDR

Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Share Resources with Service API
  - Pros
  - Cons
- Nodes Register CIDR Request
  - Pros
  - Cons

Summary

IMPORTANT: THIS KEP HAS BEEN WITHDRAWN AND THIS FEATURE WILL BE DEVELOPED OUT OF TREE Ref: https://groups.google.com/g/kubernetes-sig-network/c/nts1xEZ--gQ/m/2aTOUNFFAAAJ

Ensure Conformance Tests Do Not Require Beta APIs or Features

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

Ensure Conformance Tests Do Not Require Beta REST APIs or Features

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
  - Story 2
  - Story 3
Design Details
- Graduation Criteria
Implementation History
Infrastructure Needed
References

Release Signoff Checklist

For enhancements that make changes to code or processes/procedures in core Kubernetes i.e., kubernetes/kubernetes , we require the following Release Signoff checklist to be completed.

Ensure Secret Pulled Images

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

KEP-2535: Ensure Secret Pulled Images

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks [optional]
Alternatives [optional]
Infrastructure Needed [optional]

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Ephemeral Containers

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

KEP-277: Ephemeral Containers

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Ephemeral Inline CSI Volumes

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

KEP-596: Ephemeral Inline CSI volumes

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-goals
Proposal
- User Stories
  - Examples
- Risks and Mitigations
  - Security Considerations
Design Details
Production Readiness Review Questionnaire
Alternatives
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

etcd RangeStream

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

KEP-5966: etcd RangeStream

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Notes/Constraints/Caveats
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

EvictionRequest API

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

KEP-4563: EvictionRequest API

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Exec session identity propagation

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

KEP-6035: Exec Session Identity Propagation

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
  - Story 2
  - Story 3
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- OTel Baggage Propagation
- Keeping the CRI Primitive as a Separate KEP
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

ExecutionHook

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

ExecutionHook API Design

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Workflow
- Risks and Mitigations
Graduation Criteria
Implementation History
- User Stories
Workarounds
Alternatives
Graduation Criteria
Implementation History

Summary

This proposal is to introduce an API (ExecutionHook) for dynamically executing user’s commands in a pod/container or a group of pods/containers and a controller (ExecutionHookController) to manage the hook lifecycle. ExecutionHook provides a general mechanism for users to trigger hook commands in their containers for their different use cases. Different options have been evaluated to decide how this ExecutionHook should be managed and executed. The preferred option is described in the Proposal section. The other options are discussed in the Alternatives section.

Expanded DNS Configuration

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

KEP-2595: Expanded DNS Configuration

Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Summary

Allow kubernetes to have expanded DNS(Domain Name System) configuration.

Expose Pod Resource Request Metrics

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

KEP-1748: Expose Pod Resource Request Metrics

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements (not the initial KEP PR)
KEP approvers have approved the KEP status as implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

The current Prometheus metrics exposed by the cluster have gaps that make building accurate capacity alerts, dashboards, and ad-hoc queries more difficult than necessary and complicate the average user’s understanding of the resource model. The Kubernetes resource model is fundamental to capacity planning and error triage. It should be easy to visualize and alert on core usage and capacity through a simple set of metrics. Administrators and integrators should be able to easily graph and calculate the available and consumed resources within the cluster at any time.

Expose PSI Metrics

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

KEP-4205: Expose PSI Metrics

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
- Risks and Mitigations
Design Details - CPU - Memory - IO
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Extend kubelet pod resource assignment endpoint to return allocatable resources

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

Extend kubelet pod resource assignment endpoint to return allocatable resources

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Node Feature Discovery
  - Topology aware scheduling
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives
- Add a new endpoint

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Extend Kustomize Patches to Multiple Targets

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

Extend Kustomize Patches to Multiple Targets

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Graduation Criteria
Docs
Test plan
Implementation History
Alternatives

Summary

Currently, there are different types of patches supported in Kustomize: strategic merge patch and JSON patch .

patchesStrategicMerge:
- service_port_8888.yaml
- deployment_increase_replicas.yaml
- deployment_increase_memory.yaml

patchesJson6902:
- target:
 version: v1
 kind: Deployment
 name: my-deployment
 path: add_init_container.yaml
- target:
 version: v1
 kind: Service
 name: my-service
 path: add_service_annotation.yaml

Both types need group, version, kind and name(GVKN) of a Kubernetes resource to find the unique target to perform the patching. In strategic merge patch, GVKN is included in the patch itself. In JSON patch, the GVKN is specified in kustomization.yaml.

Extend the PodResources API to include resources allocated by DRA

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

KEP-3695: Extend the PodResources API to include resources allocated by DRA

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Extend usage of Volume DataSource to allow PVCs for Cloning

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

Allow the use of the dataSource field for clones (existing PVCs)

Summary
Motivation
- Goals
- Non-Goals
Proposal
Test Plan
- Unit tests
- E2E tests
Graduation Criteria
Implementation History
Drawbacks [optional]
Alternatives [optional]
Infrastructure Needed [optional]

Summary

This KEP proposes adding support for specifying existing PVCs in the DataSource field to indicate a user would like to Clone a Volume. Note that this KEP also applies ONLY to dynamic provisioner, and ONLY CSI Provisioner’s.

Extended NodeRestrictions for Pods

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

Extended NodeRestrictions for Pods

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Implementation History
Alternatives

Release Signoff Checklist

Extended Toleration Operators for Threshold-Based Placement

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

KEP-5471: Extended Toleration Operators for Threshold-Based Placement

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Extending Apiserver Network Proxy to handle traffic originated from Node network

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

KEP-2025: Extending Apiserver Network Proxy to handle traffic originated from Node network

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Definitions
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Extending Metrics Stability

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

KEP-3498: Extending Metrics Stability

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Extending RequestedToCapacityRatio Priority Function to support Resource Bin Packing of Extended Resources - @sudeshsh

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

ExtendingRequestedToCapacityRatio Priority Function to support Resource Bin Packing of Extended Resources

Summary
Motivation
- Goals
- Non-Goals
Proposal
Implementation History

Summary

Extend RequestedToCapacityRatio Priority Function to allow users to use the best fit polices during scheduling. It will allow users to apply bin packing on core resources like CPU, Memory as well as extended resources like accelerators.

External credential providers

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

KEP-541: External credential providers

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Drawbacks
Alternatives
- RPC vs exec
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements (not the initial KEP PR)
KEP approvers have approved the KEP status as implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

External credential providers allow out-of-tree implementation of obtaining client authentication credentials. These providers handle environment-specific provisioning of credentials (such as bearer tokens or TLS client certificates) and expose them to the client.

Fallback for HPA on failure to retrieve metrics

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

KEP-5053: Fallback for HPA External Metrics on Retrieval Failure

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1: SaaS Application Scaling on Queue Depth
  - Story 2: E-commerce Site with Multiple External Metrics
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Field status.hostIPs added for Pod

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

KEP-2681: Field status.hostIPs added for Pod

Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Summary

The proposal aims to improve the Pod’s ability to obtain the address of the node

Finalizer Protection for Service LoadBalancers

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

Finalizer Protection for Service LoadBalancers

Summary
Motivation
- Goals
Proposal
Implementation History

Summary

We will be adding finalizer protection to ensure the Service resource is not fully deleted until the correlating load balancer resources are deleted. Any service that has type=LoadBalancer (both existing and newly created ones) will be attached a service LoadBalancer finalizer, which should be removed by service controller upon the cleanup of related load balancer resources. Such finalizer protection mechanism will be released with phases to ensure downgrades can happen safely.

Fine grained Kubelet API authorization

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

KEP-2862: Fine-grained Kubelet API Authorization

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Fine grained SupplementalGroups control

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

KEP-3619: Fine-grained SupplementalGroups control

Release Signoff Checklist
Summary
- The issue
- Steps to reproduce
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Forensic Container Checkpointing

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

KEP-2008: Forensic Container Checkpointing

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Freezing `k8s.gcr.io` image registry

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

KEP-3720: Freeze `k8s.gcr.io` image registry

The change proposed by this KEP is very unusual as the engineering work will not be done in the k/k repository. However, this is a major change to the project hence the KEP.

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Communication Plan
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Gang Scheduling

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

KEP-4671: Gang Scheduling using Workload Object

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

generic ephemeral inline volumes

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

KEP-1698: generic ephemeral inline volumes

Release Signoff Checklist
Summary
Motivation
Proposal
- Risks and Mitigations
Example
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

go modules

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

go modules

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
Design Details
Implementation History
Alternatives
Reference

Release Signoff Checklist

Go workspaces for k/k

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

KEP-NNNN: Go workspaces for k/k

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Graceful Leader Transition

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

KEP-5366: Graceful Leader Transition

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Future Work (Stories)
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Graceful Node Shutdown

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

KEP-2000: Graceful Node Shutdown

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Graduate Admission Webhooks to GA

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

Admission Webhooks to GA

Summary
Motivation
- Goals
- Non-Goals
Proposal
V1 API
V1beta1 changes
Validations
Risks and Mitigations
Graduation Criteria
Post-GA tasks
Implementation History

Summary

Admission webhook is a way to extend kubernetes by putting hook on object creation/modification/deletion. Admission webhooks can mutate or validate the object. This feature has been Beta since Kubernetes 1.9. This document outline required steps to graduate it to GA.

Graduate CoreDNS to GA

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

Graduate CoreDNS to GA

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Use Cases
Graduation Criteria
Implementation History

Summary

CoreDNS is sister CNCF project and is the successor to SkyDNS, on which kube-dns is based. It is a flexible, extensible authoritative DNS server and directly integrates with the Kubernetes API. It can serve as cluster DNS, complying with the dns spec . As an independent project, it is more actively developed than kube-dns and offers performance and functionality beyond what kube-dns has. For more details, see the introductory presentation , or coredns.io , or the CNCF webinar .

Graduate CustomResourceDefinitions to GA

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

Graduate CustomResourceDefinitions to GA

Summary
Motivation
- Goals
- Non-Goals
Proposal
Test Plan
Graduation Criteria
Post-GA tasks
Implementation History

Summary

CustomResourceDefinitions (CRDs) are the way to extend the Kubernetes API to include custom resource types that behave like the native resource types. CRDs have been in Beta since Kubernetes 1.7. This document outlines the required steps to graduate CRDs to general availability (GA).

Graduate HPA v2beta2 API to GA

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

Graduate v2beta2 Autoscaling API to GA

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Implementation Details
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

This document outlines required steps to graduate autoscaling v2beta2 API to GA.

Graduate Ingress API to GA

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

KEP-1453: Graduate Ingress API to GA

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
- 1.15
- 1.18
- 1.19
- 1.20
- 1.22
Drawbacks
Alternatives
Appendix
Infrastructure Needed (optional)

Summary

Move the Ingress resource from the current API group (extensions.v1beta1) to networking.v1beta1.
Graduate the Ingress API with bug fixes to GA.

Motivation

The extensions API group is considered deprecated. Ingress is the last non-deprecated API in that group. All other types have been migrated to other permanent API groups. Such an API group migration takes three minor version cycles (~9 months) to ensure compatibility. This means any API group movement should be started sooner rather than later.

Graduate Ingress to GA

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

Graduate Ingress to GA

Summary
Motivation
- Goals
Design
Proposed roadmap
- 1.14
  - Test plan
- 1.15
- 1.16
- 1.17
- 1.18
Graduation Criteria
- API group move to networking.k8s.io/v1beta1
- GA
Implementation History
Alternatives
Appendix

Summary

Move the Ingress resource from the current API group (extensions.v1beta1) to networking.v1beta1.
Graduate the Ingress API with bug fixes to GA.

Motivation

Graduate IPv6 to beta

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

Graduate IPv6 to beta

Summary
Motivation
Proposal
Design
- Test Plan
- Graduation Criteria
Implementation History

Summary

Support for IPv6-only clusters was added in Kubernetes 1.9 as an alpha feature, allowing full Kubernetes capabilities using IPv6 networking instead of IPv4 networking. It also included support for Kubernetes IPv6 cluster deployments using kubeadm and support for the iptables kube-proxy backend using ip6tables. With version 1.13 the Kubernetes default DNS server changed to CoreDNS which has full IPv6 support.

Graduate ScheduleDaemonSetPods to GA

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

Graduate ScheduleDaemonSetPods to GA

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Implementation Details/Notes/Constraints
- Risks and Mitigations
Design Details
- Test Plan
  - Existing Tests
- Graduation Criteria
Implementation History

Release Signoff Checklist

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

ScheduleDaemonSetPods has been created in the past to schedule DaemonSet Pods by the default scheduler. We wish to graduate ScheduleDaemonSetPods feature to make scheduling decisions only in the scheduler and remove the scheduling related code in the DaemonSetController.

Graduate Server-side Get and Partial Objects to GA

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

Graduate Server-side Get and Partial Objects to GA

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
- Version Skew Strategy
Implementation History

Summary

Server-side columnar formatting and partial object metadata has been in beta since Kube 1.10 and as of 1.15 is consistently implemented and in wide use as part of kubectl and other web interfaces. This document outline required steps to graduate it to GA.

Graduate TaintNodeByCondition to GA

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

Graduate TaintNodeByCondition to GA

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Implementation Details/Notes/Constraints
Design Details
- Test Plan
  - Existing Tests
- Graduation Criteria
Implementation History

Release Signoff Checklist

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

TaintNodeByCondition has been created in the past to taint node by their conditions. We wish to graduate TaintNodeByCondition feature to make scheduling decisions based on taints instead of node conditions in the scheduler.

Growing Persistent Volume size

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

Growing Persistent Volume size

Release Signoff Checklist
Goals
Non Goals
Use Cases
Volume Plugin Matrix
Implementation Design
API and UI Design
API Changes
Production Readiness Review Questionnaire
Graduation Criteria
- Test Plan
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

(R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
(R) KEP approvers have approved the KEP status as implementable
(R) Design details are appropriately documented
(R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
(R) Graduation criteria is in place
(R) Production readiness review completed
Production readiness review approved
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Goals

Enable users to increase size of PVs that their pods are using. The user will update PVC for requesting a new size. Underneath we expect that - a controller will apply the change to PV which is bound to the PVC.

Guarantee PodDisruptionBudget When Preemption Happens

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

KEP-3280: Guarantee PodDisruptionBudget When Preemption Happens

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Handling undecryptable resources

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

KEP-3926: Handling undecryptable resources

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Harden Default RBAC Discovery ClusterRole(Binding)s

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

Harden Default RBAC Discovery ClusterRole(Binding)s

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
  - Existing customization of system:discovery
  - Dependence on existing unauthenticated behavior
Graduation Criteria
- Testing
- Documentation
Implementation History

Summary

The aim of this change is to remove the system:unauthenticated subjects from the system:discovery and system:basic-user ClusterRoleBindings, while preserving unauthenticated access to a genuinely non-sensitive subset of the current APIs (e.g. GET /healthz, GET /version). This will improve the default privacy and security posture for new clusters.

Harden Kubelet Serving Certificate Validation in Kube-API server

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

KEP-4872: Harden Kubelet Serving Certificate Validation in Kube-API server

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Hardening exec endpoints against SSRF

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

KEP-1898: Hardening exec endpoints against SSRF

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Hierarchical Namespace Controller As A Subproject

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

KEP-1687: Hierarchical Namespaces As A Subproject

Summary
Motivation
Goals
Proposal
Risks and Mitigations
Graduation Criteria
- Intake
- Beta
Alternatives
Implementation History

Summary

Hierarchical Namespace Controller makes it easier for you to create and manage namespaces in your cluster. For example, you can create a hierarchical namespace under your team’s namespace, even if you don’t have cluster-level permission to create namespaces, and easily apply policies like RBAC and Network Policies across all namespaces in your team (e.g. a set of related microservices).

Honor Persistent Volume Reclaim Policy

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

KEP-2644: Honor Persistent Volume Reclaim Policy

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Host Network Support for Windows Pods

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

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

HPA supports scaling to/from zero pods for object/external metrics

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

KEP-2021: HPA supports scaling to/from zero pods for object/external metrics

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

HTTP/2 cleartext (h2c) container probes

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

KEP-5999: HTTP/2 cleartext (h2c) container probes

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

HTTP3

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

KEP-3156: HTTP3

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
  - Story 2
- Risks and Mitigations
Design Details
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

HugePages

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

HugePages

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
Graduation Criteria for HugePageStorageMediumSize
Test Plan
Test Plan for HugePageStorageMediumSize
Production Readiness Review Questionnaire for HugePageStorageMediumSize
Implementation History
Release Signoff Checklist

Summary

A proposal to enable applications running in a Kubernetes cluster to use huge pages.

Identify Pod's OS during API Server admission

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

KEP-2802: Identify Pod’s OS during API Server admission

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Image Promoter

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

Image Promoter

Summary
Motivation
- Goals
Proposal
Graduation Criteria
Infrastructure Needed

Summary

For security reasons, we cannot allow everyone to publish container images into the official kubernetes container registry. This is why we need a process that allows us to review who built an image and who approved it to be shown in the official channels.

Image pull per runtime class

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

KEP

KEP-4216: Image pull per runtime class

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

ImageMaximumGCAge in Kubelet

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

KEP-4210: ImageMaximumGCAge in Kubelet

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

ImageVolume with an image digest

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

KEP-5365: ImageVolume with an image digest

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Immutable label selectors for all namespaces

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

KEP-2161 : Immutable label selectors for all namespaces

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Add new select-by-name capabilities to policy APIs
  - API Machinery modifications and workarounds
  - API modifications at the NetworkPolicy level
- Improve NetworkPolicy API and deprecate old fields

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Immutable Secrets and ConfigMaps

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

Immutable ephemeral volumes

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives
- Define immutability at VolumeSource level
- Optimize watches

Release Signoff Checklist

Implement maxUnavailable for StatefulSets

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

KEP-961: Implement maxUnavailable in StatefulSet

Release Signoff Checklist
Table of Contents
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
- Implementation Details
- Test Plan
Graduation Criteria
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Improve kubectl plugin resolution for non-shadowing subcommands

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

KEP-3638: Improve kubectl plugin resolution for non-shadowing subcommands

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Notes/Constraints/Caveats
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Improve pod selection accuracy across workload types

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

KEP-5625: HPA - Improve pod selection accuracy across workload types

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Improved multi-numa alignment in Topology Manager

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

KEP-3545: Improved multi-numa alignment in Topology Manager

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

In-Place Pod-Level Resources Resize

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

KEP-5419: In-Place Pod-Level Resources Resize

Release Signoff Checklist
Summary
Motivation
- Goals
- Non Goals
Proposal
- Notes/Constraints/Caveats
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Future Work

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

In-place Update of Pod Resources

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

In-place Update of Pod Resources

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- API Changes
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Allocated Resource Limits

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

In-place Update Pod Resources alognside Static CPU Manager Policy

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

KEP-5554: In-place Update Pod Resources alongside Static CPU Manager Policy

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Background
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

In-tree Storage Plugin to CSI Migration

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

In-tree Storage Plugin to CSI Migration Design Doc

Summary
- Glossary
Motivation
- Goals
- Non-Goals
Proposal
- Implementation Details/Notes/Constraints
- Risks and Mitigations
Graduation Criteria
- Alpha -> Beta
- Beta -> GA
Test Plan
Production Readiness Review Questionnaire
Implementation History

Summary

This document presents a detailed design for migrating in-tree storage plugins to CSI. This will be an opt-in feature turned on at cluster start time that will redirect in-tree plugin operations to a corresponding CSI Driver.

In-tree Storage Plugin to CSI Migration - AWS

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

In-tree Storage Plugin to CSI Migration - AWS EBS Design Doc

Summary
- New Feature Gates
Design Details
- Test Plan
Production Readiness Review Questionnaire
Implementation History

Summary

This document present as a vendor specific KEP for the parent KEP CSI Migration

This inherits all the contents from its parent KEP. It will introduce two new feature gates to be used as as described in its parent KEP. For all other contents, please refer to the parent KEP.

In-tree Storage Plugin to CSI Migration - Azuredisk

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

In-tree Storage Plugin to CSI Migration - AzureDisk Design Doc

Summary
- New Feature Gates
Production Readiness Review Questionnaire
Implementation History

Summary

This document present as a vendor specific KEP for the parent KEP CSI Migration

This inherits all the contents from its parent KEP. It will introduce two new feature gates to be used as as described in its parent KEP. For all other contents, please refer to the parent KEP.

In-tree Storage Plugin to CSI Migration - Azurefile

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

In-tree Storage Plugin to CSI Migration - Azure File Design Doc

Summary
- New Feature Gates
Production Readiness Review Questionnaire
Design Details
- Test Plan
Implementation History

Summary

This document present as a vendor specific KEP for the parent KEP CSI Migration

This inherits all the contents from its parent KEP. It will introduce two new feature gates to be used as as described in its parent KEP. For all other contents, please refer to the parent KEP.

In-tree Storage Plugin to CSI Migration - Ceph Cephfs

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

In-tree Storage Plugin to CSI Migration - Ceph Cephfs Design Doc

Summary
- New Feature Gates
Design Details
- Test Plan
Production Readiness Review Questionnaire
Implementation History

Summary

This document present as a vendor specific KEP for the parent KEP CSI Migration

This inherits all the contents from its parent KEP. It will introduce two new feature gates to be used as described in its parent KEP. For all other contents, please refer to the parent KEP.

In-tree Storage Plugin to CSI Migration - Ceph RBD

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

In-tree Storage Plugin to CSI Migration - Ceph RBD Design Doc

Summary
- New Feature Gates
Design Details
- Test Plan
Production Readiness Review Questionnaire
Implementation History

Summary

This document present as a vendor specific KEP for the parent KEP CSI Migration

This inherits all the contents from its parent KEP. It will introduce two new feature gates to be used as described in its parent KEP. For all other contents, please refer to the parent KEP.

In-tree Storage Plugin to CSI Migration - Cinder

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

In-tree Storage Plugin to CSI Migration - OpenStack Cinder Design Doc

Summary
- New Feature Gates
Production Readiness Review Questionnaire
Implementation History

Summary

This document present as a vendor specific KEP for the parent KEP CSI Migration

This inherits all the contents from its parent KEP. It will introduce two new feature gates to be used as as described in its parent KEP. For all other contents, please refer to the parent KEP.

In-tree Storage Plugin to CSI Migration - GCE PD

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

In-tree Storage Plugin to CSI Migration - GCE Design Doc

Summary
- New Feature Gates
Production Readiness Review Questionnaire
Design Details
- Test Plan
Implementation History

Summary

This document present as a vendor specific KEP for the parent KEP CSI Migration

This inherits all the contents from its parent KEP. It will introduce two new feature gates to be used as as described in its parent KEP. For all other contents, please refer to the parent KEP.

In-tree Storage Plugin to CSI Migration - Portworx

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

KEP-2589: In-tree Storage Plugin to CSI Migration - Portworx Design Doc

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

In-tree Storage Plugin to CSI Migration - vSphere

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

In-tree Storage Plugin to CSI Migration - vSphere Design Doc

Summary
- New Feature Gates
Design Details
Production Readiness Review Questionnaire
Implementation History

Summary

This document present as a vendor specific KEP for the parent KEP CSI Migration

This inherits all the contents from its parent KEP. It will introduce two new feature gates to be used as as described in its parent KEP. For all other contents, please refer to the parent KEP.

Indexed Job

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

KEP-2214: Indexed Job

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

IngressClass Namespaced Params

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

KEP-2365: IngressClass Namespaced Params

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

This KEP proposes adding new Scope and Namespace fields to the IngressClass ParametersRef field.

Insecure Backend Proxy

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

KEP-1295: Insecure Backend Proxy

When trying to get logs for a pod, it is possible for a kubelet to have an expired serving certificate. If a client chooses, it should be possible to bypass the default behavior of the kube-apiserver and allow the kube-apiserver to skip TLS verification of the kubelet to allow gathering logs. This is especially important for debugging misbehaving self-hosted clusters.

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks [optional]
Alternatives [optional]
Infrastructure Needed [optional]

Release Signoff Checklist

Integrate CSI Volume attach limits with cluster autoscaler

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

KEP-5030: Integrate Volume Attach limit into cluster autoscaler

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Cluster Autoscaler changes
- Scaling a node-group that already has one or more nodes.
- Scaling from zero
Kubernetes Scheduler change
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Integrate Workload APIs with Job Controller

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

KEP-5547: Integrate Workload APIs with Job Controller

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Interactive(-i) flag to kubectl delete for user confirmation

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

KEP-3895: Interactive(-i) flag to kubectl delete for user confirmation

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Confirming Per Resource (yes/no)
- Confirming Per Resource with Yes to All Option(yes/no/yes to all)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Introduce kuberc

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

KEP-3104: Introduce kuberc

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Introduce MatchLabelKeys and MismatchLabelKeys to PodAffinity and PodAntiAffinity

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

KEP-3633: Introduce MatchLabelKeys and MismatchLabelKeys to PodAffinity and PodAntiAffinity

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- implement as a new enum in LabelSelector
  - Example
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

IP/CIDR Validation Improvements

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

KEP-4858: IP/CIDR Validation Improvements

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Ratcheting validation for immutable fields
- Fixing pre-existing invalid values

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

IPVS Load Balancing Mode in Kubernetes

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

IPVS Load Balancing Mode in Kubernetes

Note: This is a retroactive KEP. Credit goes to @m1093782566, @haibinxie, and @quinton-hoole for all information & design in this KEP.

Important References: https://github.com/kubernetes/community/pull/692/files

Summary
Motivation
Proposal
Graduation Criteria
- Beta -> GA
- GA -> Future
Implementation History
Drawbacks [optional]
Alternatives [optional]

Summary

We are building a new implementation of kube proxy built on top of IPVS (IP Virtual Server).

Issue Triage Workflow and Automation

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

KEP-1553: Issue Triage Workflow and Automation

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Implementation History
Drawbacks
Alternatives
Infrastructure Needed

Release Signoff Checklist

Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements (not the initial KEP PR)
KEP approvers have approved the KEP status as implementable
Design details are appropriately documented
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
Contributor documentation has been created in kubernetes/community

Summary

To ease the burden of SIG/area reviewers/approvers, we would like to prescribe a triage workflow and supporting automation.

Job API managed-by label

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

KEP-4368: Support managedBy field for Jobs

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Job success/completion policy

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

KEP-3998: Job success/completion policy

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Job tracking without lingering Pods

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

KEP-2307: Job tracking without lingering Pods

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Notes/Constraints/Caveats (Optional)
- Risks and Mitigations
Design Details
Monitoring Pods with finalizers
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

k8s.io Group Protection

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

k8s.io Group Protection

Summary
Motivation
- Goals
- Non-Goals
Proposal
References
Alternatives considered
Implementation History

Summary

API groups are organized by namespace, similar to java packages. authorization.k8s.io is one example. When users create CRDs, they get to specify an API group and their type will be injected into that group by the kube-apiserver.

KEP Template

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

KEP-2763: Support Ambient Capabilities in Kubernetes.

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
  - Story 2
  - Story 3
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

KEP Template

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

KEP-3314: CSI Changed Block Tracking

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

KEP Template

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

KEP-3659: ApplySet: kubectl apply –prune redesign and graduation strategy

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Background
Proposal
Design Details: ApplySet Specification
Design Details: Kubectl Pruning
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- OwnerRefs
- ManagedFields
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

KEP Template

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

KEP-4940: Add Pod Security Admission (PSA) to block setting `.host` field from ProbeHandler and LifecycleHandler

Release Signoff Checklist
Summary
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

KEP Template

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

KEP-5468: Invariant Testing

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Implement outside of test framework
- Collect data, and scan for it externally
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

KEP Template

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

KEP-85: Graduate PodDisruptionBudget to stable

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

KMS Observability

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

KEP-3130: KMS Observability

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
- Test Plan
- Graduation Criteria
  - Alpha
  - Beta
  - GA
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

KMS v2 Improvements

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

KEP-3299: KMS v2 Improvements

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives
Infrastructure Needed

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kube Proxy component configuration updates and graduation

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

KEP-784: Kube Proxy component configuration graduation

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

kube-apiserver identity

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

KEP-1965: kube-apiserver identity

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Caveats
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kube-proxy improved ingress connectivity reliability

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

KEP-3836: Kube-proxy improved ingress connectivity reliability

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risk
- Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

The service controller in the Kubernetes cloud controller manager (KCCM) configures the load balancer and its corresponding health check (HC) following service related events. The configured health check is then used by the load balancer as to determine which instances are candidates for traffic load balancing. For certain cloud providers (GCP): the KCCM configures the HC to target the Kubernetes service proxy for this information. In this KEP we will focus on Kube-proxy, since it’s the only service proxy under the responsibility of the Kubernetes project.

kubeadm component config management

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

Kubeadm config file graduation

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

kubeadm customization with patches

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

kubeadm join --control-plane workflow

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

kubeadm phases to beta

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

kubeadm-for-windows

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

kubeadm-machine-output

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

Kubectl Commands In Headers

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

KEP-859: kubectl commands in headers

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

kubectl debug

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

KEP-1441: kubectl debug

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

kubectl default container

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

KEP-2227: default container behavior

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubectl events

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

KEP-1440: kubectl events

Release Signoff Checklist
Summary
Motivation
Proposal
- User Stories
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubectl Explain OpenAPIv3

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

KEP-3515: OpenAPI v3 for kubectl explain

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Implement proto.Models for OpenAPI V3 data
- Custom User Templates
Future Work
- Other template outputs
  - HTML
  - Markdown

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubectl Plugins

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

Kubectl Plugins

Summary
Motivation
Proposal
Graduation Criteria
Implementation History
Drawbacks
Future Improvements/Considerations

Summary

This proposal introduces the main design for a plugin mechanism in kubectl. The mechanism is a git-style system, that looks for executables on a user’s $PATH whose name begins with kubectl-. This allows plugin binaries to override existing command paths and add custom commands and subcommands to kubectl.

kubectl return code normalization

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

KEP-2551: kubectl exit code standardization

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
  - Story 2
  - Story 3
- Risks and Mitigations
  - Feature Gating
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubectl Server-Side Apply by default

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

KEP-3805: Server-Side Apply default in Kubectl

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
  - Story 2
  - Story 3
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubectl Subresource Support

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

KEP-2590: Kubectl Subresource Support

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
  - Story 2
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

kubectl-diff

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

kubectl-diff

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
- Risks and Mitigations
Design Details
Implementation History

Release Signoff Checklist

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

kubectl diff is a feature that has been available in Kubernetes for a few releases now (since v1.13) and is planning to go GA in 1.18. It provides a very simple UX to display how the changes to a configuration will affect the state of the cluster.

Kubelet client certificate bootstrap and rotation

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

KEP-266: Kubelet client certificate bootstrap and rotation

Release Signoff Checklist
Summary
- Goals
Proposal
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
KEP approvers have approved the KEP status as implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
User-facing documentation has been created at https://kubernetes.io/docs/tasks/tls/certificate-rotation/

Summary

Currently, a kubelet has a certificate/key pair that authenticates the kubelet to the kube-apiserver. The certificate is supplied to the kubelet when it is first booted, via an out of cluster mechanism. This proposal covers a process for obtaining the initial cert/key pair and rotating it as expiration of the certificate approaches.

Kubelet Credential Providers

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

KEP-2133: Kubelet Credential Providers

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubelet CRI support

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

Kubelet CRI support

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubelet endpoint for device assignment observation details

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

Kubelet endpoint for device assignment observation details

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1: Cluster administators: easier monitoring
  - Story 2: Device Vendors: decouple monitoring from device lifecycle management
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubelet endpoint for pod resource assignment

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

Kubelet endpoint for pod resource assignment

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
- User Stories
  - Device aware CNI plugin
  - Topology aware scheduling
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubelet Evented PLEG for Better Performance

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

KEP-3386: Kubelet Evented PLEG for Better Performance

Release Signoff Checklist
Acknowledgements
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubelet Exec Probe Timeouts

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

KEP-1972: Kubelet Exec Probe Timeouts

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Implementation History
Drawbacks
Alternatives
Production Readiness Review Questionnaire

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubelet limit of Parallel Image Pulls

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

KEP-3673: Kubelet limit of Parallel Image Pulls

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
- Alpha
- Beta
- GA
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubelet OpenTelemetry Tracing

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

KEP-2831: Kubelet Tracing

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Other OpenTelemetry Exporters

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubelet Resource Metrics Endpoint

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

Kubelet Resource Metrics Endpoint

Release Signoff Checklist
Summary
Motivation
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives Considered
- gRPC API
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubernetes Bootstrap Checkpointing Proposal

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

Kubernetes Component Health SLIs

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

KEP-3466: Kubernetes Component SLIs

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubernetes CSI release and CI process

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

kubernetes-csi-release-process

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
Implementation History
Drawbacks
Alternatives
Infrastructure Needed

Summary

The Kubernetes Storage SIG maintains a set of components under the kubernetes-csi GitHub organization. Those components are intentionally not part of core Kubernetes even though they are maintained by the Kubernetes project.

Kubernetes Dual-stack Support

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

IPv4/IPv6 Dual-stack

Summary
Motivation
- Goals
- Non-Goals
Proposal
Implementation History
Alternatives
- Dual-stack at the Edge
- Variation: Single-Stack Service CIDRs
  - Changes Required
Test Plan
Graduation Criteria
Production Readiness Review Questionnaire

Summary

This proposal adds IPv4/IPv6 dual-stack functionality to Kubernetes clusters. This includes the following concepts:

Kubernetes Metrics Overhaul

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

Kubernetes Metrics Overhaul

Summary
Motivation
- Goals
- Non-Goals
Proposal
Test Plan
Deprecation Plan
Graduation Criteria
Implementation History

Summary

This Kubernetes Enhancement Proposal (KEP) outlines the changes planned in the scope of an overhaul of all metrics instrumented in the main kubernetes/kubernetes repository. This is a living document and as existing metrics, that are planned to change are added to the scope, they will be added to this document. As this initiative is going to affect all current users of Kubernetes metrics, this document will also be a source for migration documentation coming out of this effort.

Kubernetes VolumeAttributesClass and ModifyVolume

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

KEP-3751: Kubernetes Volume Provisioned IO

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Proposed Changes
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kubernetes Yearly Support Period

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

Kubernetes Yearly Support Period

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
- Component changes
Test Plan
Implementation History
Drawbacks
Alternatives
Infrastructure Needed

Release Signoff Checklist

Kubetest2 CI Migration

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

KEP-2464: Kubetest2 CI migration

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kui Graphical Terminal Enhancements

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

KEP-2257 Kui: Kubectl Graphical Plugins

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
- Test Plan
- Graduation Criteria
  - Alpha -> Beta Graduation
  - Beta -> GA Graduation
Implementation History

Summary

This enhancement offers a kubectl plugin framework that allows kubectl and kubectl plugins the ability to have graphical popups in response to normal CLI commands. To provide a popup-from-terminal experience, this project leverages the Kui project.

Kustomize

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

Kustomize

Summary
Motivation
Proposal
Graduation Criteria
Implementation History
Drawbacks
Alternatives
FAQs

Summary

Declarative specification of Kubernetes objects is the recommended way to manage Kubernetes production workloads, however gaps in the kubectl tooling force users to write their own scripting and tooling to augment the declarative tools with preprocessing transformations. While most of these transformations already exist as imperative kubectl commands, they are not natively accessible from a declarative workflow.

Kustomize Components

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

Kustomize Components

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kustomize Exec Secret Generator

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

Kustomize Exec Secret Generator

Summary
Motivation
- Goals
- Non-Goals
Proposal
- New Flags
- Example
Risks and Mitigations
- Security
Alternatives Considered
- Git Style Plugins
  - Enable Plugins with Environment Variables
Graduation Criteria
- Graduation to GA
  - Audit Command
  - More OS Specific install locations
Testing and documentation.
- Testing
- Documentation
Implementation History

Summary

The ability to generate Secrets using exec was removed in kustomize v2 because of security concerns about users kustomizing malicious kustomization.yamls and thereby providing a path for kustomization.yaml’s publishers to execute arbitrary commands on the machines of any user who applies the kustomization.yaml.

Kustomize File Processing Integration

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

Kustomize File Processing Integration

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Specifics
- Risks and Mitigations
Graduation Criteria
- Evaluate and decide
- Implement
Docs
Test plan
- Version Skew Tests
Implementation History
Alternatives

Summary

This is a follow up to KEP Kustomize Subcommand Integration

Kustomize was introduced as subcommand of kubectl to allow users to build their kustomizations directly. However users need to pipe the kustomize output to other commands in order to use the kustomizations.

Kustomize Function Catalog

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

KEP-2906: Kustomize Function Catalog

Release Signoff Checklist
Summary
- Key terminology
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kustomize Generators and Transformers

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

Kustomize Generators and Transformers

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Implementation History
Drawbacks [optional]
Alternatives [optional]

Release Signoff Checklist

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

Enable users to extend Kustomize Transformers and Generators through exec plugins. Kustomize provides Resource Config to plugins through STDIN, and plugins emit Resource Config back to Kustomize through STDOUT.

Kustomize Plugin Composition API

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

KEP-2299: Kustomize Plugin Composition API

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kustomize Plugin Graduation

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

KEP-2953: Kustomize plugin graduation

Release Signoff Checklist
Summary
- Key terminology
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)
Appendix
- Current Plugin Compatibility Grid

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Kustomize Secret Generator Plugins

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

Kustomize Secret K:V Generator Plugins

Summary
Motivation
- Goals
- Non-Goals
Proposal
Risks and Mitigations
Graduation Criteria of plugin framework
- Alpha status
- Graduation to beta
Implementation History

Summary

Kustomize users want to generate Kubernetes Secret objects from general key:value (KV) pairs where the value is supposed to be a secret. Users want to generate these pairs through integration with secret management tools (e.g. see comments on [692][execRemoval]).

Kustomize Subcommand Integration

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

Kustomize Subcommand Integration

Summary
Motivation
Proposal
- Justification for this approach
- Justification for follow up
Kustomize Example
- Implementation Details/Notes/Constraints
- Risks and Mitigations
Graduation Criteria
Implementation History
Alternatives

Summary

Kustomize was developed as a subproject of sig-cli by kubectl maintainers to address a collection of issues ) creating friction for declarative workflows in kubectl (e.g. kubectl apply). The goal of the kustomize subproject was to bring this functionality back to kubectl to better complement kubectl apply and other declarative workflow commands.

KYAML

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

KEP-5295: Introducing KYAML, a safer, less ambiguous YAML subset / encoding

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Notes/Constraints/Caveats
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Less object serializations

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

Less object serializations

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Implementation History
Alternatives

Release Signoff Checklist

Liveness Probe Grace Period

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

KEP-2238: Liveness Probe Grace Periods

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Configuration example
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Local Ephemeral Storage Capacity Isolation

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

Local Ephemeral Storage Capacity Isolation

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
- Test Plan
Graduation Criteria
Production Readiness Review Questionnaire
Implementation History
Drawbacks [optional]
Infrastructure Needed [optional]
References

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Local Persistent Volumes

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

Local Persistent Volumes

Summary
Motivation
- Goals
- Non-Goals
Background
Proposal
Test Plan
Graduation Criteria
- Alpha -> Beta
- Beta -> GA
Implementation History
Infrastructure Needed

Summary

This document presents a detailed design for supporting persistent local storage, as outlined in Local Storage Overview .

Mailing List Guidelines

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

The Kubernetes mailing list or Google Groups functions as the primary means of asynchronous communication for the project’s Special Interest Groups (SIG) , Working Groups (WG) , and large subprojects.

Code of conduct
Admins
- Mailing list owners
Moderation
- Moderator expectations and guidelines
  - New user posting queue
  - Annual permissions review
Mailing list creation
- Prerequisites for creating a mailing list
- Create the leads and members mailing lists
Set up shared calendars and meeting with a mailing list
Archive a mailing list

Code of conduct

The Kubernetes project adheres to the community Code of Conduct throughout all platforms and includes all communication mediums.

Make a control-plane's kubelet point to the local API Server on kubeadm join

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

Make kube-proxy service abstraction optional

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

Make kube-proxy service abstraction optional

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
Implementation History

Summary

In a cluster that has a service mesh a lot of the work being done by kube-proxy is redundant and wasted. Specifically, services that are only reached via other services in the mesh will never use the service abstraction implemented by kube-proxy in iptables (or ipvs). By informing the kube-proxy of this, we can lighten the work it is doing and the burden on its proxy backend.

Make Kubernetes aware of the load balancer behaviour

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

KEP-1860 Make Kubernetes aware of the LoadBalancer behaviour

Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
  - Story 2
  - Story 3
- Risks and Mitigations
Drawbacks
Alternatives
Design Details
Test Plan
Graduation Criteria
Production Readiness Review Questionnaire
Implementation History

Summary

The different kube-proxy implementations (at least ipvs and iptables), as of today, are binding the External IPs of the LoadBalancer Service to each node. (iptables are creating some rules to redirect packets directly to the service and ipvs is binding the IP to one interface on the node). This feature exists because:

Make nftables the default kube-proxy backend

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

KEP-5343: Make nftables the default kube-proxy backend

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Manifest Based Admission Control Config

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

KEP-5793: Manifest Based Admission Control Config

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Memory Manager

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

KEP-1769: Memory Manager

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Appendix

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Memory QoS

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

KEP-2570: Support Memory QoS with cgroups v2

Release Signoff Checklist
Latest Update
- Previous Status (v1.36)
- Previous Status (v1.28)
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

(R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
(R) KEP approvers have approved the KEP status as implementable
(R) Design details are appropriately documented
(R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
(R) Graduation criteria is in place
(R) Production readiness review completed
(R) Production readiness review approved
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Latest Update

Targeting Beta in v1.37. Rollback cleanup is now fully implemented. Cgroup v2 memory knobs (memory.min, memory.low, memory.high) are properly cleared when the MemoryQoS feature gate is disabled. Node e2e tests cover memory protection, throttling, and rollback cleanup. Benchmark testing validates memory.high throttle behavior, tiered memory protection, and rollback safety. See Beta v1.37 for details.

Metrics Stability Framework

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

KEP-1209: Metrics Stability Framework

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
- Current list of stable metrics:

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

metrics.k8s.io API definition

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

KEP-5207: metrics.k8s.io API definition

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Migrate Gateway API to k8s.io Group

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

KEP-2829: Migrate Gateway API to k8s.io Group

Summary
Motivation
- Goals
Proposal
- Risks and Mitigations
Design Details
- Graduation Criteria
  - Alpha
  - Beta
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

Note: This KEP is primarily for tracking purposes. The code for this feature is all out-of-tree, but the using the k8s.io API group requires API review. Most sections of this KEP will be marked as not applicable.

Migrate kubernetes-mixin from kubernetes-monitoring to kubernetes-sigs organization

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

KEP-5905: Migrate `kubernetes-mixin` from `kubernetes-monitoring` to `kubernetes-sigs` organization

Please note that quite a few sections from the template were dropped in this KEP, as they are not applicable to the nature of the proposal.

Migrating API objects to latest storage version

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

Migrating API objects to latest storage version

Summary
Motivation
- Goals
Proposal
Beta Graduation Criteria
Alternatives
- update-storage-objects.sh

Summary

We propose a solution to migrate the stored API objects in Kubernetes clusters. In 2018 Q4, we will deliver a tool of alpha quality. The tool extends and improves based on the oc adm migrate storage command.

Minimize iptables-restore input size

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

KEP-3453: Minimizing iptables-restore input size

Summary
Motivation
- Goals
- Non-Goals
Proposal
- General Plan
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

The performance of kube-proxy’s iptables mode in large clusters could be greatly increased by optimizing its calls to iptables-restore. Although this is a small change in terms of code size, it has a large effect on kube-proxy operation, and could potentially completely break clusters (if the code was buggy), so we have decided to treat it as a KEP-able feature.

minReadySeconds for StatefulSets

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

KEP-2599: minReadySeconds for StatefulSets

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Moderation Rules and Responsibilities

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

This page describes the rules and best practices for people chosen to moderate Kubernetes communications channels. This includes Github, Slack, forums, mailing lists, YouTube, Zoom, and any property listed in the SIG Contributor Experience charter .

Check the centralized list of administrators for contact information.
Some Kubernetes properties, like the Twitter account, are managed by the CNCF.

Selection of Moderators
- Moderators Pro Tempore
Rotation of Moderators
Roles and Responsibilities
Violations
Escalation Procedures
Platform Specific Guidelines
References and Resources

Selection of Moderators

Each Kubernetes property has a certain set of moderators who are responsible for keeping it safe and a fun place to participate.

Moderator list

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

The following people are responsible for moderating/administrating Kubernetes communication channels and their home time zone. See our moderation guidelines for policies and recommendations.

Mailing Lists
- kubernetes-dev
GitHub
Discuss
- Administrators
- Regional Category Moderators
YouTube Channel
Slack
Zoom

Mailing Lists

kubernetes-dev

Administrators

SIG Contributor Experience Leads

Primary Moderators

Primary moderators seats: 6

More granular Job failure reasons for PodFailurePolicy

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

KEP-4443: More granular Job failure reasons for PodFailurePolicyRule

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Move cgroup v1 in maintenance mode

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

KEP-4569: Moving cgroup v1 support into maintenance mode

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Move EndpointSlice Reconciler into Staging

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

KEP-3685: Move EndpointSlice Reconciler into Staging

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Dependencies
- Risks and Mitigations
Design Details
- Test Plan
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

Move the EndpointSlice reconciler and it’s dependencies to staging so that the reconciler logic be reused by out-of-tree EndpointSlice controllers.

Some changes are needed in pkg/controller/endpointslice to move the reconciler code to staging/src/k8s.io/endpointslice and then import it as Go module. These changes include making private methods public and updating the import paths.

Move ExternalDNS out of Kubernetes incubator

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

Move ExternalDNS out of Kubernetes incubator

Summary
Motivation
- Goals
Proposal
Details

Summary

ExternalDNS is a project that synchronizes Kubernetes’ Services, Ingresses and other Kubernetes resources to DNS backends for several DNS providers.

The projects was started as a Kubernetes Incubator project in February 2017 and being the Kubernetes incubation initiative officially over, the maintainers want to propose the project to be moved to the kubernetes GitHub organization or to kubernetes-sigs, under the sponsorship of sig-network.

Move Kubectl Code into Staging

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

KEP-1020: Move Kubectl Code into Staging

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Risks and Mitigations
Graduation Criteria
Testing
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Move mount library to staging

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

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Implementation History
Alternatives

Release Signoff Checklist

KEP approvers have set the KEP status to implementable
[NA] Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
[NA] Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
[NA] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
[NA] Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

The mount library in k8s/utils/mount is shared by both in-tree volume plugins and external CSI drivers. We propose moving this library from k8s/utils to a separate k/k staging repo in order to leverage existing k/k e2e tests and infrastructure, and make it easier to backport fixes to the mount library to Kubernetes

Move ReferenceGrant to sig-auth API Group

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

KEP-3766: Move ReferenceGrant to SIG Auth API Group

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Open Questions
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Move Storage Version Migrator in-tree

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

KEP-4192: Move Storage Version Migrator in-tree

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
- APIs to move
  - Changes while we move above APIs in-tree:
Former, out-of-tree implementation
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Streaming List (considered, rejected)
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Moving ComponentConfig API types to staging repos

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

Multi Scheduling Profiles

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

Multi Scheduling Profiles

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
- Test Plan
- Graduation Criteria
  - Alpha (v1.18):
  - Beta (v1.19):
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

(R) kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
(R) KEP approvers have set the KEP status to implementable
(R) Design details are appropriately documented
(R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
(R) Graduation criteria is in place
(R) Production readiness review completed
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

As workloads in clusters become more heterogeneous, it is natural that they have different scheduling needs.

Multi-Cluster Services API

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

KEP-1645: Multi-Cluster Services API

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Constraints and Conflict Resolution
Implementation History
Alternatives
Infrastructure Needed

Release Signoff Checklist

Enhancement issue in release milestone, which links to KEP dir in kubernetes/enhancements (not the initial KEP PR)
KEP approvers have approved the KEP status as implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Summary

There is currently no standard way to connect or even think about Kubernetes services beyond the cluster boundary, but we increasingly see users deploy applications across multiple clusters designed to work in concert. This KEP proposes a new API to extend the service concept across multiple clusters. It aims for minimal additional configuration, making multi-cluster services as easy to use as in-cluster services, and leaves room for multiple implementations.

Multiple Service CIDRs

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

KEP-1880: Multiple Service CIDRs

Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

Allow to dynamically expand the number of IPs available for Services.

Mutable CSINode Allocatable Property

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

KEP-4876: Mutable CSINode Allocatable Property

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Mutable Node Scheduling Directives for Jobs

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

KEP-2926: Allow updating scheduling directives of jobs

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives
- Alternative 2: allow updating jobs with no restrictions.
- Allow updating all suspended jobs

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Mutable PersistentVolume Node Affinity

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

KEP-5381: Mutable PersistentVolume Node Affinity

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Integrate with the CSI spec and VolumeAttributesClass
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Mutable Pod Resources for Suspended Jobs

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

KEP-5440: Allow updating pod template resources (CPU, memory, GPU, extended resources) of suspended jobs

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
  - Story 2
  - Story 3
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Delete and Recreate Jobs
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Mutating Admission Policies

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

KEP-3962: Mutating Admission Policies

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Alternative 2: Introduce new syntax
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Namespace Selector for Pod Affinity

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

KEP-2249: Namespace Selector For Pod Affinity

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
- User Stories (Optional)
  - Story 1
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Alternatives
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Native Histogram Support for Kubernetes Metrics

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

KEP-5808: Native Histogram Support for Kubernetes Metrics

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Increase Classic Histogram Bucket Count
Infrastructure Needed (Optional)
References

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Network Policy status subresource

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

Summary

NetworkPolicy objects does not contain a status subresource. This KEP proposes to add this subresource in NetworkPolicy objects, allowing Network Policy providers to provide feedback to users whether a NetworkPolicy and its features has been properly parsed.

New CPUManager Static Policy which spread hyperthreads across physical CPUs to better utilize CPU Cache

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

KEP-4176: A new static policy to prefer allocating cores from different CPUs on the same socket

Release Signoff Checklist
Summary
Goals
Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

New Event API GA Graduation

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

New Event API GA Graduation

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Considerations
Production Readiness Review Questionnaire
Implementation History
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

New kubelet gRPC API with endpoint returning local pods information

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

KEP-4188: New Kubelet gRPC API with endpoint returning local Pods information

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Future work

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

New label for trusted PR identification

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

New label for trusted PR identification

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
Future evolutions
References
Implementation History

Summary

This document describes a major change to the way the trigger plugin determines if test jobs should be started on a pull request (PR).

New TopologyManager Policy which configure the value of maxAllowableNUMANodes

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

KEP-4622: New TopologyManager Policy which configure the value of maxAllowableNUMANodes

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

nftables Localhost NodePort Userspace Proxy

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

KEP-6032: nftables Localhost NodePort Userspace Proxy

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- HostPort DaemonSet Proxy

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Node Declared Features

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

KEP-5328: Node Declared Features

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Existing Mechanisms and Limitations
Proposal
- Node Declared Features Requirements
User Stories
- Feature Rollout Challenges with Version Skew
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Node Lifecycle Conditions

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

KEP-NNNN: Node Lifecycle Conditions

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Node log query

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

KEP-2258: Node log query

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Node System Partition

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

KEP-5894: Node System Partition

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Alternative cgroup hierarchies
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Node system swap support

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

KEP-2400: Node memory swap support

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Just set –fail-swap-on=false
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Node Topologies via Downward API

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

KEP-4742: Node Topology Labels via Downward API

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Node Topology Manager

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

KEP-693: Node Topology Manager

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
References
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

NodeConformance and NodeFeature labels cleanup

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

KEP-3041: NodeConformance, NodeFeature, and Feature Gate labels cleanup

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

NodeLocal DNS Cache

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

NodeLocal DNS Cache

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
- Alpha -> Beta Graduation
- Beta -> GA Graduation
Rollout Plan
Implementation History
Drawbacks [optional]
Alternatives [optional]

Summary

This proposal aims to improve DNS performance by running a dns caching agent on cluster nodes as a Daemonset. In today’s architecture, pods in ClusterFirst DNS mode reach out to a kube-dns serviceIP for DNS queries. This is translated to a kube-dns endpoint via iptables rules added by kube-proxy. With this new architecture, pods will reach out to the dns caching agent running on the same node, thereby avoiding iptables DNAT rules and connection tracking. The local caching agent will query kube-dns for cache misses of cluster hostnames(cluster.local suffix by default).

Nominated node name for an expected pod placement

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

KEP-5278: Nominated node name for an expected pod placement

Release Signoff Checklist
Summary
Motivation
Proposal
- User Stories (Optional)
  - Story 1: Prevent inappropriate scale downs by Cluster Autoscaler
  - Story 2: Scheduler can resume its work after restart
- Risks and Mitigations
Design Details
GA
- Upgrade / Downgrade Strategy
- Version Skew Strategy
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

non graceful shutdown

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

KEP-2268: Non graceful node shutdown

Release Signoff Checklist
Summary
Motivation
Proposal
- Handle the Return of Shutdown Node
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives
- Node fencing
- SafeDetach Option

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Notification Management Best Practices

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

The Kubernetes Mailing list or Google Groups functions as the primary means of asynchronous communication for the project’s Special Interest Groups (SIG) and Working Groups (WG) . That’s why you may want to set your filters in your email account to attain a good signal-to-noise ratio with regards to the mailing list messages and GitHub notifications. All the steps below are for Gmail users, however similar filters can be made in other email clients.

Object Storage Support

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

KEP-1979: Object Storage Support

Release Signoff Checklist
Summary
Motivation
- Goals
  - Functionality
  - System Properties
- Non-Goals
Proposal
- User Personas
Design details
Alternatives Considered
Production Readiness Review Questionnaire
Implementation History
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

OCI images as VolumeSource

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

KEP-4639: OCI VolumeSource

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Online Growing Persistent Volume Size

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

Online Growing Persistent Volume Size

Summary
Motivation
- Goals
- Non-Goals
Proposal
Test Plan
Graduation Criteria
- Alpha to Beta
- Beta to GA
Implementation History

Summary

This feature enables users to expand a volume’s file system by editing a PVC without having to restart a pod using the PVC.

Only allow anonymous auth for configured endpoints

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

KEP-4633: Only allow anonymous auth for configured endpoints

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)
Possible Future Improvements

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

OpenAPI Enum Types

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

KEP-2887: OpenAPI Enum Types

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Do Not Break Existing Clients

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

OpenAPI Features in Kustomize

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

KEP-2206: OpenAPI Features in Kustomize

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
- Test Plan
- Graduation Criteria
  - Alpha -> Beta Graduation
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

OpenAPI V3

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

KEP-2896: OpenAPI V3

Release Signoff Checklist
Summary
Motivation
- Goals
  - Transparency in the OpenAPI
- Non-Goals
Proposal
- Notes/Constraints/Caveats (Optional)
  - Future Work
  - OpenAPI V2 plan
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Opportunistic batching

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

KEP-5598: Opportunistic batching

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Comparison with Equivalence Cache (circa 2018)
- New Rescore Extension Point
Future work
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Optionally Disable Node Ports for Service Type=LoadBalancer

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

KEP-1864: Optionally Disable Node Ports for Service Type=LoadBalancer

Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- APIServer Flag
- Service Type=LoadBalancerWithoutNodePorts

Summary

Today, a Kubernetes Service Type=LoadBalancer will always allocate a node port for every service port. Though most implementations of Service Type=LoadBalancer do require node ports, there are several implementations that do not. This KEP proposes to add a new field to Service to opt out of node port allocation for loadbalancers.

Ordered Namespace Deletion

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

KEP-5080: Ordered Namespace Deletion

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Using finalizers to define the deletion ordering
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

OwnerReference Resource Field

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

OwnerReference Resource Field

Summary
Motivation
- Goals
- Non-Goals
Proposal
References
Alternatives considered
Implementation History

Summary

OwnerReferences are used to track garbage collection references. Today they use kind. This is a serialization format not a URL to access on the kube-apiserver. To find a URL, a series of upwards of 20 discovery calls are made to find every resource in the cluster to find a list of potential resources (URLs more or less). This approximates user intent and mostly works, but it is inefficient and unnecessarily vulnerable to network outages.

Paginated API Lists

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

KEP-365: Paginated API Lists

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

pdb-support-for-custom-resources-with-scale-subresource

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

PDB support for custom resources with scale subresource

Summary
Motivation
- Goals
Proposal
- Implementation Details/Notes/Constraints
- Risks and Mitigations
Design Details
- Test Plan
- Graduation Criteria
Implementation History

Summary

Pod Disruption Budget (PDB) is a Kubernetes API that limits the number of pods of a collection that are down simultaneously from voluntary disruptions. PDBs allows a user to specify the allowed disruption through either min available or max unavailable number of pods. In order to support PDBs where max number of unavailable pods is set, the PDB controller needs to be able to look up the desired number of replicas. It does this by looking at the controller(s) (as specified by the owner ref) for the pods covered by the PDB. Currently only four of the basic workload controllers are supported for PDBs, namely Deployment, StatefulSet, ReplicaSet and ReplicationController.

Per-container ulimits configuration

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

KEP-5758: Per-container ulimits configuration

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Per-plugin callback functions for efficient requeueing in the scheduling queue

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

KEP-4247: Per-plugin callback functions for efficient requeueing in the scheduling queue

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Return QueueImmediately, QueueAfterBackoff, and QueueSkip from QueueingHintFn instead of introducing new status Pending
- Implement Blocked status to block a next scheduling retry until the plugin returns Queue
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Per-Pod PID Limit

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

KEP-6063: Per-Pod PID Limit

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

PersistentVolume last phase transition time

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

KEP-3762: PersistentVolume last phase transition time

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pid Limiting

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

Pid Limiting

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
- Pod to Pod pid isolation
- Node to Pod pid isolation
Implementation History

Summary

A proposal to enable isolation of pid resources. It proposes a mechanism to enable pod-to-pod PID isolation as well as node-to-pod PID isolation.

Placement Decision API

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

KEP-5313: PlacementDecision API

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod Certificates

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

KEP-4317: Pod Certificates

Release Signoff Checklist
Summary and Motivation
Motivation
- Goals
- Non-Goals
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod Generation

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

KEP-5067: Pod Generation

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod Healthy Policy for PDB

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

KEP-3017: Unhealthy Pod Eviction Policy for PDBs

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Abandoned Alternative Implementation
- Changes to the disruption controller
- Changes to the definition of healthy in a PDB according to the policy used.
Future Work

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod Index Label

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

KEP-4017: Pod Index Label for StatefulSets and Indexed Jobs

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Add pod index as annotation
- Add pod index as both label and annotation
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod Level Resource Specifications

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

KEP-2837: Pod Level Resource Specifications

Release Signoff Checklist
Summary
Motivation
- Goals
- Non Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- VPA
Future Work

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod lifecycle sleep action

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

KEP-3960: Introducing Sleep Action for PreStop Hook

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
  - Story 2
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod Mutable Scheduling Directives

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

KEP-3838: Pod Mutable Scheduling Directives

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Alternatives
- Use webhooks to inject affinities
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod networking ready condition

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

KEP-3085: Pod Conditions for Starting and Completion of Sandbox Creation

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod Overhead

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

Pod Overhead

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Drawbacks
Alternatives
- Introduce pod level resource requirements
- Leaving the PodSpec unchanged
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
KEP approvers have set the KEP status to implementable
Design details are appropriately documented
Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
Graduation criteria is in place
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in kubernetes/website , for publication to kubernetes.io
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Note: Any PRs to move a KEP to implementable or significant changes once it is marked implementable should be approved by each of the KEP approvers. If any of those approvers is no longer appropriate than changes to that list should be approved by the remaining approvers and/or the owning SIG (or SIG-arch for cross cutting KEPs).

Pod Priority Based Graceful Node Shutdown

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

KEP-2712: Pod Priority Based Graceful Node Shutdown

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod Ready++

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

Pod Ready++

Summary
Motivation
- Goals
- Non-Goals
Proposal
Graduation Criteria
Implementation History
Alternatives - Why not fix the workloads? - Why not extend container readiness?

Summary

This proposal aims to add extensibility to pod readiness. Besides container readiness, external feedback can be injected into PodStatus and influence pod readiness. Thus, achieving pod “ready++”.

Pod Scheduling Readiness

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

KEP-3521: Pod Scheduling Readiness

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod Topology Spread

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

KEP-895: Pod Topology Spread

Release Signoff Checklist
Terms
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Story 1
  - Story 2
- Risks and Mitigations
Design Details
Alternatives
Impact to Other Features
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

(R kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
(R) KEP approvers have set the KEP status to implementable
(R) Design details are appropriately documented
(R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
(R) Graduation criteria is in place
(R) Production readiness review completed
Production readiness review approved
“Implementation History” section is up-to-date for milestone
User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

Terms

Topology: describe a series of worker nodes which belongs to the same region/zone/rack/hostname/etc. In terms of Kubernetes, they’re defined and grouped by node labels.
Affinity: if not specified particularly, “Affinity” refers to NodeAffinity, PodAffinity and PodAntiAffinity.
CA: Cluster Autoscaler. CA is a tool that automatically adjusts the size of the Kubernetes cluster upon specific conditions.

Summary

The PodTopologySpread feature gives users more fine-grained control on distribution of pods scheduling, so as to achieve better high availability and resource utilization.

Pod-level Checkpoint/Restore

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

KEP-5823: Pod-Level Checkpoint/Restore

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Open Questions
Drawbacks
Alternatives
- Rejected Approaches

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Pod-Level Resource Managers

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

KEP-5526: Pod Level Resource Managers

Release Signoff Checklist
Glossary
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with R are required prior to targeting to a milestone / release.

Pop pod from backoffQ when activeQ is empty

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

KEP-5142: Pop pod from backoffQ when activeQ is empty

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
- Low priority pod could be chosen to pop, even if high priority pod has a slightly later backoff expiration
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
- Move pods in flushBackoffQCompleted when activeQ is empty

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Prefer Nominated Node

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

KEP-1923: Prefer Nominated Node

Release Signoff Checklist
Summary
Motivation
- Goals
Proposal
- User Stories (Optional)
- Notes/Constraints/Caveats (Optional)
Design Details
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Preferred Fit Strategy

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

KEP-2458: Resource Fit Scoring Strategy

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories (Optional)
  - Story 1
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

PreferSameZone and PreferSameNode Traffic Distribution

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

KEP-3015 PreferSameZone and PreferSameNode Traffic Distribution

Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - PreferClose vs PreferSameZone
  - DNS
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives

Summary

Discussion about trying to add “prefer same node” behavior to TrafficDistribution: PreferClose (#4931 ) led to the conclusion that any attempt to change the semantics of PreferClose would inevitably have either too many false positives or too many false negatives.

PreQueueingHint Extension Point for Scheduler Event Processing

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

KEP-6132: PreQueueingHint Extension Point for Scheduler Event Processing

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
- Risks and Mitigations
Design Details
Production Readiness Review Questionnaire
Alternatives
- PodGroup (GenericWorkload) Interaction
- Other Alternatives
Implementation History

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Presubmit config inside the tested repo

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

Presubmit config inside the tested repo

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
  - Security
  - Components that need the Presubmit configuration but do not have a git ref to work on
- Graduation Criteria
  - Alpha -> Beta Graduation
  - Beta -> Stable Graduation
Implementation History

Release Signoff Checklist

N/A - this KEP is related to code solely in kubernetes/test-infra that is not being used as part of the development or release process for kubernetes/kubernetes

Prevent unauthorised volume mode conversion

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

KEP-3141: Prevent unauthorised volume mode conversion

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed (Optional)

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Prioritization on Volume Capacity

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

KEP-1845: Prioritization on volume capacity

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- User Stories
  - Volumes with close capacity are preferred
  - Different weights for different classes
Design Details
Alternatives
- Maintain multiple storage classes for different storage capacities
Production Readiness Review Questionnaire
Implementation History
Drawbacks

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Priority and Fairness for API Server Requests

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

KEP-1040: Priority and Fairness for API Server Requests

Release Signoff Checklist
Summary
Motivation
Proposal
Design Details
Production Readiness Review Questionnaire
Implementation History
Drawbacks
Alternatives
Infrastructure Needed

Release Signoff Checklist

Items marked with (R) are required prior to targeting to a milestone / release.

Production Readiness Review Process

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

Production Readiness Review Process

Release Signoff Checklist
Summary
Motivation
- Goals
- Non-Goals
Proposal
- Risks and Mitigations
Design Details
- Phase 1 - Research and Pilot
- Phase 2 - Implementation
Implementation History

Welcome on Kubernetes Contributors

Kubernetes Meet and Greet

About

Details

Maintainer Summit Europe 2026

About

📅 Schedule & Participation

Eligibility

2019 Awards

SIG Cloud Provider

SIG Instrumentation

SIG Release

SIG Scheduling

SIG Storage

SIG Windows

WG Multitenancy

2020 Awards

API Machinery

Architecture

Authentication

CLI

Cloud Provider

Contributor Experience

Cluster Lifecycle

Documentation

Instrumentation

Network

Release

Scheduling

Storage

Testing

Usability

Windows

2021 Awards

API Machinery

Apps

Architecture

2022 Awards

API Machinery

2023 Awards

API Machinery

Apps

2024 Awards

API Machinery

2025 Awards

API Machinery

Community Calendar

How to Join

Notice

Register for the event

How to Join

Notice

Register for the event

Section 1: Starting Out

Welcome to Kubernetes!

Section 1: Starting Out

What you are about to learn

Services and Requests

GitHub requests

Organization membership

Contributor Cheatsheet

Helpful Resources

Getting Started

SIGs and Other Groups

Community

Workflow

Tests

Important Email Aliases

Other Useful Links

Communicating Effectively on GitHub

How to be Excellent to Each Other

Events and Activities

Notice

Events

Kubernetes Contributor Awards

Events and Activities

Notice

Events

Kubernetes Contributor Awards

Kubernetes Community Values