OLM: A Declarative Way to Install, Manage, and Upgrade Operators
summary
OLM installs and upgrades operators via container-hosted “operator bundles” that put /manifests and /metadata inside an image, letting the cluster pull, verify, and mirror operator content; the catalog composes bundles into an index image (today backed by SQLite and a gRPC server) and already publishes over 100 operators. OLM enforces dependency resolution, safe upgrade paths authored by operators, supports disconnected installs via image registries, and is evolving toward a declarative index config and pluggable content providers so single-bundle installs and helm-like types work too.
AI-written summary · about
chapters (8)
- 0:00Introduction to Operators
- 10:46Packaging and Delivery
- 11:56Operator Bundle Format
- 13:23Composition with Indexes
- 15:04Disconnected Environments
- 16:22Future Roadmap for OLM
- 17:46OLM V2 Development
- 18:57Community and Q&A
related talks
34mWhat's New In Operator Framework?
39mWriting a Kubernetes/Openshift Operators Using Golang
28mSmooth Operator - A Rough Guide to Kubernetes Operators - Olive Power, VMware
45mKubernetes Operators: Operating Cloud Native services at scale
42mOpenSearch in Kubernetes: Helm Charts and Operator
24mAutomating Stateful Apps with Kubernetes Operators
27mBeing a Good Citizen of the Multi-operator World
23mStop Writing Operators