The Backbone of Kubernetes APIs: A Deep Dive into SIG Architecture's API Governance Subproject

Introduction

In the Kubernetes ecosystem, APIs are the lifeblood that connects components, users, and external systems. Ensuring these APIs remain stable yet adaptable is the mission of the API Governance subproject under SIG Architecture. This article explores the goals, scope, and leadership of this vital group, based on insights from its lead, Jordan Liggitt.

The Journey of Jordan Liggitt: From First PR to Subproject Lead

Early Kubernetes Experiences

Jordan Liggitt describes himself as a Christian, husband, father of four, software engineer at Google by day, and an amateur musician. Though born in Texas, he has spent most of his life in North Carolina. His journey with Kubernetes began in 2014 while working on authentication and authorization at Red Hat. His very first pull request (PR) attempted to integrate an OAuth server directly into the Kubernetes API server. The PR never left work-in-progress status, and after six months, he closed it without merging. Instead, he adopted a different approach—layering the solution on top of the core API server in a separate project, foreshadowing the importance of clear API boundaries.

Evolving into Leadership

Undeterred by that early setback, Liggitt remained deeply involved. He contributed to building Kubernetes authentication and authorization capabilities, and helped define and evolve core APIs from early beta versions like v1beta3 to v1. In 2016, he was recognized as an API reviewer, and a year later, he became an API approver. Around 2019, he joined the API Governance subproject, eventually co-leading it alongside the code organization subproject within SIG Architecture. He also serves as a tech lead for SIG Auth.

Goals and Scope of API Governance

Beyond the REST API: The Full Surface Area

When people think of Kubernetes APIs, they often picture the REST API—the biggest and most obvious one. However, Liggitt emphasizes that the API surface encompasses much more: command-line flags, configuration files, how binaries are executed, how components communicate with back-end services like the container runtime, and how data is persisted. Each of these surfaces has a narrower audience but still demands careful design and governance.

Balancing Stability and Innovation

The primary goal of API Governance is to strike a delicate balance between stability and innovation. Stability alone is easy—just never change anything—but that would stifle evolution. Conversely, too much change risks breaking users and systems. The subproject therefore establishes guidelines that allow the ecosystem to grow without compromising reliability. This philosophy applies across all API surfaces, ensuring that changes are thoughtful and consistent.

Quality Gates and the Role of API Governance

During the lifecycle of a Kubernetes change, API Governance acts as a gatekeeper to maintain consistency and quality. While specific gates are detailed in the full interview, the subproject is involved at multiple points: through pre-release guidelines, milestone reviews, and retrospective feedback. Liggitt notes that governance does not just occur during release cycles; it is embedded in ongoing design discussions. Every API addition, deprecation, or modification must pass scrutiny to ensure it aligns with the project’s long-term vision.

Internal processes such as review gates and scope definitions help the subproject stay proactive rather than reactive. This layered approach—from early design to final approval—ensures that Kubernetes APIs remain coherent, usable, and forward-compatible.

Conclusion

API Governance is a cornerstone of Kubernetes architecture, ensuring that the platform’s many interfaces—from REST endpoints to CLI flags—are thoughtfully designed and resilient. Under leadership like Jordan Liggitt, the subproject continues to evolve, balancing the tension between stability and innovation. For developers and operators alike, understanding this governance layer provides insight into why Kubernetes APIs feel robust yet flexible, and how each change contributes to the ecosystem’s long-term health.

This article is part of a series spotlighting SIG Architecture subprojects.