Extending the Kubernetes API: What the Docs Don't Tell You
summary
Shows how to actually extend Kubernetes by building a custom API server and controller that persist alerts to etcd and notify Pushbullet, proving the approach end-to-end with a working pager demo; uses generated artifacts from client-gen, deepcopy-gen, informer/lister and conversion-gen so controllers use shared caches and work queues; demonstrates runtime conversion via internal API objects between v1alpha1 and v1beta1; warns against mutating the informer cache and explains dependency pinning for generators.
AI-written summary · about
chapters (33)
- 0:00Introduction
- 1:05Kubernetes API
- 2:37NCD Operator
- 3:18Control Loop Pattern
- 3:39Role Binding
- 4:18CTL
- 4:31Custom resource definitions
- 5:10Custom API service
- 6:45API aggregation
- 6:58API generators
- 9:52Comments
- 10:52API Pager
- 11:09Pushbullet
- 11:37Demo
- 12:05Pager
- 12:40Shirt
- 12:51Face
- 13:05What have I used
- 13:15What is all of this
- 13:59Follow the rules
- 14:32Client Generator
- 14:49Event Handler
- 15:31Conversion Generator
- 16:24Code Walkthrough
- 19:00API Server
- 19:19New API Version
- 20:03Custom API Server Demo
- 21:45Converting Alert Spec
- 22:01External vs Internal API
- 22:57Pager Demo
- 23:58Wrapup
- 25:13Questions
- 27:52Shared Index Informer
related talks
44mExtending Kubernetes
06mExtending the Kubernetes API
08mKubernetes: The API of Everything
01h 01mKubernetes – going beyond the basics
05mKubernetes API Explained
40mExtension API Server in Kubernetes: When CRD Is Not Enough
31mKubernetes is Your Platform: Design Patterns For Extens...
59mKubernetes - going beyond the basics