Kubernetes API Highlight Christos Gkoros API Designer @ Postman
A presentation at Kubernetes Athens meetup in March 2024 in Athens, Greece by Christos Gkoros
Kubernetes API Highlight Christos Gkoros API Designer @ Postman
API Design I work with engineering teams during their API Design phase: 1. Why we need this API? 2. Who consumes the API? 3. Make decisions about the API
API Design System ● ● ● ● ● Identify patterns that can be reused. Compare with well known APIs Document these patterns Promote their re-usability Incrementally establish a design system that produces consistent APIs
Let’s skip kubectl and other tools that aim to make things easy
● CORE - /api/v1 /api/v1/pods /api/v1/namespaces/… /api/v1/services ● GROUPS - /apis/{{group}}/{{versions}} /apis/apps/deployments/v1/ /apis/authentication.k8s.io/v1/ All these endpoints are documented in a definition available at /openapi/v2 Let’s see it in action! But first:
Authorization Inception: This will actually use the POST /apis/rbac.authorization.k8s.io/v1/clusterroles endpoint
DEMO TIME!!! A flow scaling our deployment based on external conditions (APIs) This is not intended production
THANKS https://www.linkedin.com/in/christos-gkoros/ All resources can be found at: https://www.postman.com/gkoroscapidesign/works pace/athens-kubernetes-meetup-kubernetes-api-hi ghlight CREDITS: This presentation template was created by Slidesgo, including icons by Flaticon, and infographics & images by Freepik
