The state of Package Management on Kubernetes
summary
Compares Helm, Timoni and Glasskube with concrete tradeoffs: Helm templates are powerful but messy, Helm stores releases as double‑base64 gzipped secrets, CRD upgrades and umbrella dependencies break in practice and OCI charts are not searchable; Timoni bundles packages as OCI images. Glasskube ships as Apache‑2.0 in early 2024, has 600+ GitHub stars and CNCF visibility, runs a client/server model with package CRDs, Argo CD integration, a GUI and renovate support, and demoed installing cloud‑native‑pg, Argo CD and Captain which pulled s‑manager into the correct namespace.
AI-written summary · about
chapters (5)
- 0:00Introduction and motivation
- 10:15Helm overview and challenges
- 15:55Glass Cube package management
- 19:09Live demo of Glass Cube
- 28:03Q&A session
related talks
31mIntroducing Timoni the Next-Gen Package Manager for Kubernetes
27mKubernetes Package Management Using Unix with Carvel
05mKeynote: Breaking Tradition: The Future of Package Management with Kubernetes
26mAre We Stuck With Helm Forever? A Landscape of Cloud Native CNF Manag...
35mLearn About Helm And Its Ecosystem
34mIntro: Helm
40mTreating Kubernetes as a Linux Distro: APT-Style Packaging with FluxCD
41mHelm - the Better Way to Deploy on Kubernetes