Juju & Charmed Operators Past, Present and Future!
summary
Juju 3.0 slims the codebase (roughly 120,000 lines trimmed), rebuilds CI, deprecates Windows charms and introduces Pebble as the Kubernetes sidecar runtime with files API, layered process config, health checks and one‑shot command execution; it adds secrets as first‑class primitive with rotation and Kubernetes/HashiCorp Vault backends; ships a Terraform provider as a Juju client; plans to replace MongoDB with DQLite for much faster bootstrap; and will embed a Starlark scripting engine to enable controller‑side automation and the new stacks model for bundle-aware upgrades and lifecycle operations.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:47Operator Framework
- 3:00Juju Controller
- 4:05Pebble
- 5:34Pebble Files API
- 9:31Charm Production Practices
- 11:25Charmed Style Guide
- 12:20Juju 30 Updates
- 13:46Terraform Provider
- 15:31Secrets
- 18:03Whats Next
- 19:43Starlock
- 21:43Stack
related talks
11mInterview
42mPythonic deployment of (Python) applications
27mBroader Adoption of FINOS Projects, Case Studies - Charming Legend and Waltz
39mTo the Clouds: Why you should deploy to the cloud even if you don't want to
23mDeploying OpenSearch Solutions on Hybrid Multi-Cloud Environments
35mSubverting the Monolith with Principles and Tooling
29mMutability, Declarability, and Disposability, oh my!
14mThe HashiStack from the Perspective of a Web Dev