Jordan Liggitt leads the Kubernetes API Governance subproject, aiming to balance API stability with innovation. This project oversees all Kubernetes APIs, including command-line flags and configuration files, not just the REST API. Ensuring consistency and quality involves guidelines, conventions, and automated tools like linters. API Governance provides input during both API design and implementation, especially through the KEP process. The introduction of Custom Resources was a turning point, expanding API possibilities and necessitating enhanced validation. API Governance collaborates with SIG Architecture and API Machinery to define conventions and ensure API Machinery's consistent use. Involvement in the project increases before enhancements and code freezes in the release cycle. New contributors should start by following API changes and observing the review process. The project prioritizes compatibility and stability for users, even if it requires extra effort. The goal of API Governance is to plan for future API evolution while minimizing compatibility breaks. They consider mistakes will be made, and prepare to improve while keeping compatibility promises.