This is the fifth interview of a SIG Architecture Spotlight series that covers the different subprojects, and we will be covering SIG Architecture: API Governance.
In this SIG Architecture spotlight we talked with Jordan Liggitt, lead of the API Governance sub-project.
Introduction FM: Hello Jordan, thank you for your availability. Tell us a bit about yourself, your role and how you got involved in Kubernetes.
JL: My name is Jordan Liggitt.

K8S Contributors

Jordan Liggitt, lead of Kubernetes SIG Architecture's API Governance subproject, discusses how the team maintains stability and consistency across all Kubernetes APIs while enabling innovation. The subproject reviews API changes at design or implementation stages, enforces conventions through guidelines and automated tools, and ensures conceptual integrity. Custom Resource Definitions marked a watershed moment, shifting from fully controlled APIs to user-defined ones, requiring new validation capabilities. API Governance balances backward compatibility promises with evolution, assuming future knowledge will require design flexibility while protecting users from breaking changes.

Spotlight on SIG Architecture: API Governance

The impact of Custom Resource Definitions