Upgrade Yourself to the Business Class
summary
Argues that staying current reduces CVEs (example: a 2021 Strimzi image shows 12 critical and 63 high CVEs) and makes it easier to get help; demonstrates two upgrade patterns: step-by-step upgrades (operator apply, Kafka version change, then inter‑broker protocol — effectively 3 manual steps) and skip‑version jumps that update operator and Kafka together; shows recorded demos of operator rolling updates, CR edits to change Kafka/version/protocol, and successful end-to-end upgrades.
AI-written summary · about
chapters (14)
- 0:00Upgrading software
- 2:57Risks of outdated software
- 7:12Bugs and security in old versions
- 8:14Kubernetes and Strimzi compatibility
- 11:44Help for old versions
- 12:05Step-by-step Strimzi upgrades
- 16:00Live demo: step-by-step upgrade
- 22:22Skipping versions
- 25:15Live demo: skipping versions
- 28:54Downgrades and limits
- 32:07Upgrading Strimzi components
- 33:10Kafka clients compatibility
- 34:14Key takeaways
- 36:24Q&A
related talks
28mPhased upgrades of Strimzi managed Kafka fleets
50mOps issues
50mDevOps Patterns & Antipatterns for Continuous Software Updates
49mKeeping Up with the Times, or How to Upgrade PostgreSQL
46mThe Cycle of Upgrades
37mSafe Upgrades: From Tombstones to Recommendations
34mUpdate RabbitMQ now!
30mDevOps Patterns and Antipatterns for Continuous Software Updates