Writing kubectl Plugins for Everyone: Develop, Package & Distribute
summary
Kubernetes rebuilds its kubectl plugin model into a simple exec-based system where any executable named kubectl-foo binary on PATH becomes a subcommand; plugins inherit kubectl env and set its exit code. The ecosystem ships a manager, krew plugin manager, that downloads archives, verifies sha256, creates symlinks and a centralized index for discoverability. A YAML plugin manifest declares platform-specific URIs and install steps so a single release can package Mac/Linux/Windows binaries and be installed or removed cleanly.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:15Kubernetes
- 0:47Old plugins model
- 1:24What?
- 2:03Why develop plugins?
- 2:52enhance kubectl
- 3:43official command vs plugin
- 4:56plugin vs standalone
- 5:32encapsulate workflows
- 7:09How plugins work?
- 7:55Demo: sample plugin
- 9:41What's next?
- 10:28Consistency
- 11:55Naming
- 15:05Problem: plugin management
- 16:52Meet Krew
- 17:23Demo: plugin user
- 19:58Krew overview
- 21:29Packaging with krew
- 21:56Demo: plugin developer
- 25:27Plugin manifests
- 26:50Call to action
- 27:55How to get involved / contact
related talks
29mCreate & Distribute a Plugin for K8s in Minutes? Easy!
36mKubectl Plugins 101
28mThe Building Blocks of DX: K8s Evolution From CLI to GitOps
29mWhat's New With Kubectl and Kustomiz...
10mKeynote: Unleashing the Power of Kubectl
20mBuildKit CLI for kubectl: A New Way to Build Container Images
19mUnleashing the power of kubectl
17mOwn your YAML: extending Kustomize via Plugins