Crafting Seamless Development: Improving Kubernetes Operator Developer Experience
summary
Work on the Machine Config Operator for OpenShift and Go cuts a slow “edit-compile-run-debug” cycle into concrete fixes: initial sandbox clusters take 30–60 minutes and installs fail ~80–85% of the time; integration CI runs take ~4 hours. Incremental steps — using cache volumes, concurrent multi-stage container builds (jobs flag) to hit ~30s, binary injection to drop full-cycle checks to ~5 minutes, fast unit suites at ~15s, plus the MCO Builder Tool, fake client/ envtest and toolbox containers — reduce iteration time by over 50% and automate verification.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:27Agenda
- 1:19Developer Move Development
- 2:39What is Kubernetes Development
- 5:02Kubernetes Operators
- 5:41Machine Configuration Operator
- 7:50Operator pods
- 8:25Challenges
- 13:56Solution
- 21:00Development Loop
- 22:15Summary
related talks
55mFrom my Machine to the Cloud with Cloud-Native Tools
33mFrom Slow To Pro: Accelerating Kubernetes Native Devel...
43mLessons learned writing 10+ Kubernetes Operators
36mHow to run like a startup with enterprise Kubernetes
13mInterview of Jerome Petazzoni
17mtalk Kubernetes with
44mPerformance and Scalability Tuning Kubernetes for OpenShift and Docker
42mKubernetes native development workflows