Beyond the Install: Take Full Ownership of Your Strimzi Cluster
summary
Explains concrete operations: regular operator releases every one to two months, patch releases usually only for the latest minor, and Kafka support limited to the two most recent minor versions (example: 0.45 got two yearlong patches). Describes tooling and risks: Quay outages, SBOMs and image signatures, respins using UBI base images with tags like 1.0.0-1, and CI-heavy system tests that require Kubernetes and take hours. Recommends mirror container images and Helm charts, build from source and run system tests to own upgrades and CVE fixes.
AI-written summary · about
chapters (5)
- 0:00Strimzi ownership intro
- 2:46What maintainers provide
- 11:57User responsibilities
- 18:56Supply chain security
- 25:39Summary & Q&A
related talks
04mProject Lightning Talk: Strimzi – What's New and What's Next
28mPhased upgrades of Strimzi managed Kafka fleets
34mHow to Survive Managing Strimzi in an Enterprise
19mKeynote: Strimzi Past, Present and Future
21mKeynote: Strimzi past, present and future
31mSimplifying Apache Kafka on Kubernetes With Strimzi
29mWhen GitOps goes wrong, and other challenges for Strimzi platform teams
42mTransition to Apache Kafka on Kubernetes With Strimzi