Extensibility without chaos: lessons from building Cozystack
summary
Cozystack tightens its core instead of exposing endless knobs: an initial sprawling spec is reduced so the etcd deployment surface becomes four strings, and the project ships a working etcd operator and uses Cilium for networking. Rather than per-app config fields, ownership mapping from pod → controller → Helm chart enables transparent security-group semantics and an API dashboard v0.3. For backups, a pluggable strategy API (Cluster API–inspired) lets app authors provide their own controllers so diverse backup workflows actually work.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:47Building Cozystack as universal platform
- 3:55Pitfalls of unbounded customization
- 7:32Go’s monotonic time lessons
- 13:18Simplicity in Cozystack
- 17:51Kubernetes extension points
- 20:00Backup strategies with extensibility
- 24:42Key takeaways
- 25:44Q&A
related talks
19mSimplify Kubernetes Operator Development With a Modular Design Pattern
22mCreating a Micro Open-Source Community with Helm
25mThe New Stack Makers Virtual Pancake Breakfast + Podcast: IT, Developer Strategies, and Open Source
22mOpen Standards: Anchoring Extensibility for Cloud-Native Tooling
30mSturdy Clouds Creating Resilient Software Defined Data Centers
36mModernizing OpenStack with Kubernetes, Cluster API, Keycloak (..and Rust?)
36mOne Platform Could Not Fit Them All
05mInfrastructure Extensibility at Home and DevOps