enhancements

This repository is the enhancement tracking repo for Kubernetes releases, owned by SIG Architecture. It holds issues and KEPs (Kubernetes Enhancement Proposals) that act as umbrellas for new enhancements added to Kubernetes. An enhancement usually spans multiple releases and can be tracked as a backlog item before work begins; it may be filed once there is consensus in at least one Kubernetes SIG. The README defines what counts as an enhancement through rough heuristics. An enhancement is generally something a blog post would be written about after release, requires multiple parties/SIGs/owners to complete, graduates from one stage to another (alpha to beta, beta to GA), needs significant effort or changes Kubernetes substantially, impacts UX or operations enough that users need retraining, or is something users will notice and rely on. It is unlikely to be an enhancement if it is implemented via a CustomResourceDefinition, fixes a flaky test, refactors code, only improves performance visible as faster API operations or control loops, or merely adds error messages or events. New enhancement issues should be created after circulating the idea (community meetings, SIG meetings, mailing lists, or a kubernetes/kubernetes issue), optionally prototyping in a fork, identifying people who agree to work on it, and being ready to act as project manager. The README notes many enhancements take several releases and roughly 9 months to a year to reach Stable. Enhancements are tracked because users expect to rely on them long-term, so the project holds them to high standards of conceptual integrity, consistency, thorough testing, and complete documentation. Tracking issues provide a checklist with different approvers for different aspects across the Alpha, Beta, and Stable stages. Comments on enhancement issues are for requesting review or clarification on process, updating status, or linking related issues in other repos; design, code, or docs details should be discussed in linked issues or PRs. As of the 1.26 release, enhancements are visualized in Enhancements Tracking Boards, with milestone links from 1.26 through 1.38. Before 1.26, tracking spreadsheets were used, and an archive of those sheets is referenced. The current release cycle points to the 1.38 release information in the sig-release repository. Exceptions to enhancement milestone dates are handled by the Release Team per their documentation. Labels include `sig/foo` for the owning SIG, `kind/feature` to mark an issue as an enhancement, and `stage/{alpha,beta,stable}` for the feature process stage, each set via comment commands. A glossary document defines terminology and acronyms used in the Enhancements subproject.