- API Review
- Code Freeze
- Exceptions
- Enhancements Freeze
- Kubernetes Enhancements Proposal (KEP)
- Production Readiness Review (PRR)
The API review process is intended to maintain logical and functional integrity of the API over time, the consistency of user experience and the ability of previously written tools to function with new APIs.
If an enhancement is considered to be changing the Kubernetes core API in any way,
a mandatory API review is required. An Enhancement owner should proactively request an
API review for an enhancements PR by adding a /label api-review comment.
The status of an API review can be found in the
API review backlog.
More details can be found in Kubernetes API Review Process.
All enhancements going into the release must be code-complete by the code freeze deadline. Any unmerged pull requests in k/k repo for the upcoming release milestone will be removed by the Release Team and will require an approved exception to have the milestone added back by the Release Team.
More details can be found in Code Freeze.
When an enhancement fails to meet the release deadline, Enhancement owner must file an exception request addressed to SIG sponsoring the enhancement, the Release Team, and SIG Release to gain approval. The Release Team will be responsible for approving or rejecting exceptions and the decision will be based on discussion with the sponsoring SIG's chairs/leads and any other participating SIG's chairs/leads.
More details can be found in Exceptions to Milestone Enhancement Complete dates.
All enhancements going into the release must meet the required criteria by the enhancements freeze deadline.
Any enhancements that do not meet all of the criteria will be removed from tracking for the upcoming release. Any unmerged pull requests in k/enhancements repo for the upcoming release milestone will be removed by the Release Team and will require an approved exception to have the milestone added back and the enhancement tracked again by the Release Team.
More details can be found in Enhancements Freeze.
A Kubernetes Enhancement Proposal is a way to propose, communicate and coordinate on new efforts for the Kubernetes project.
A KEP should be created after socializing an idea with the sponsoring and participating SIGs. To create a KEP, the KEP template should be used and follow the process outlined in the template.
Use the definition of what is an Enhancement to determine if a KEP is required.
More details can be found in Kubernetes Enhancement Proposals and Enhancements.
Production Readiness Reviews are intended to ensure that features merging into Kubernetes are observable, scalable and supportable, can be safely operated in production environments, and can be disabled or rolled back in the event they cause increased failures in production.
PRR approval is a requirement for the enhancement to be part of the upcoming release and all enhancements owners must submit a KEP for production readiness approval before the Enhancements Freeze deadline.
To request a Production Readiness Review, assign a PRR approver from the prod-readiness-approvers
list in the OWNERS_ALIASES
file and reach out to the production readiness approvers in slack channel #prod-readiness.
More details can be found in Production Readiness Review Process and PRR KEP.