# Spotlight on SIG Architecture: Enhancements

DevFeed: [Spotlight on SIG Architecture: Enhancements](<https://devfeed.tech/articles/spotlight-on-sig-architecture-enhancements-17585.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2025/01/21/sig-architecture-enhancements/>)

Author: The Kubernetes Authors

Published: 2025-01-21T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [Processes](<https://devfeed.tech/topics/processes.md>)

Tags: [interview](<https://devfeed.tech/tags/interview.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [release](<https://devfeed.tech/tags/release.md>), [series](<https://devfeed.tech/tags/series.md>)

## AI overview

An interview with Kirsten Garrison, lead of the Kubernetes SIG Architecture Enhancements subproject, explains how Kubernetes Enhancement Proposals support feature design and significant project changes. It describes the KEP approval process across release cycles and feature phases.

## Source excerpt

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. Kirsten Garrison (KG): I'm a lead of the Enhancements subproject of SIG-Architecture and currently work at Google. I first got involved by contributing to the service-catalog project with the help of Carolyn Van Slyck . With time, I joined the Release team , eventually becoming the Enhancements Lead and a Release Lead shadow. While on the release team, I worked on some ideas to make the process better for the SIGs and Enhancements team (the opt-in process) based on my team's experiences. Eventually, I started attending Subproject meetings and contributing to the Subproject's work. FSM: You mentioned the Enhancements subproject: how would you describe its main goals and areas of intervention? KG: The Enhancements Subproject primarily concerns itself with the Kubernetes Enhancement Proposal (KEP for short)--the "design" documents required for all features and significant changes to the Kubernetes project. The KEP and its impact FSM: The improvement of the KEP process was (and is) one in which SIG Architecture was heavily involved. Could you explain the process to those that aren't aware of it? KG: Every release , the SIGs let the Release Team know which features they intend to work on to be put into the release. As mentioned above, the prerequisite for these changes is a KEP - a standardized design document that all authors must fill out and approve in the first weeks of the release cycle. Most features will move through 3 phases : alpha, beta and finally GA so approving a feature represents a signi