1/5 KubeCon is over, and I'm traveling back from Amsterdam to Prague. This was the first #KubeCon #Strimzi took part in the project pavilion with our own kiosk. A week ago, when going to KubeCon, I was a bit nervous about how it would go.
Another major milestone on the road to #Strimzi 1.0.0! If you want to learn more about our journey, come to the talk I have with Paolo Patierno at #KubeCon in Amsterdam next week ... kccnceu2026.sched.com/event/2EF6l/...
On 9th March 2018, we released #Strimzi 0.2.0 - the first Strimzi release following the operator pattern. So ... HAPPY BIRTHDAY STRIMZI! 🥳🥂🥳
#Strimzi 0.51.0 is out! 🥳
It supports #ApacheKafka 4.1.0, 4.1.1, and 4.2.0. And #Kubernetes 1.30+. Checkout the release page or our "What's new" video to learn more about this release:
➡️ github.com/strimzi/stri...
🎦 youtu.be/qHYpOhZACzY
Next stop: #Strimzi 1.0.0!
March is here. And that means #KubeCon starts in a few weeks. With Paolo Patierno, we will talk about #Strimzi 1.0.0 in the maintainer track. And for the first time, we will also have a Strimzi kiosk in the project pavilion. Hope to see you in Amsterdam!
Хаос-инжиниринг Strimzi Kafka: проверка устойчивости к сбоям через Chaos Mesh Цель проекта — проверить отказоустойчи...
#kafka #strimzi #chaos #mesh
Origin | Interest | Match
We have released #Strimzi 0.50.1. This patch release addresses a few minor bug fixes and dependency updates. It also fixes two new Strimzi CVEs: CVE-2026-27133 and CVE-2026-27134! Please check the new release and the CVEs, and upgrade if needed:
➡️ github.com/strimzi/stri...
Last chance to apply for the current term of LFX Mentorship. One of the projects is a #Strimzi plugin for the @headlamp.dev ... github.com/headlamp-k8s...
1/2 In-place Pod resizing was one of the interesting features that graduated to stable in #Kubernetes 1.35. While in-place changes to memory are limited in Java, it might help to give #Strimzi users some more flexibility.
Start a new week with a new #Strimzi release: Strimzi 0.50.0 is out! Check out our "What's New" video and the release notes, and start upgrading:
🎬 youtu.be/BPNt4Z7g3p4
🔗 github.com/strimzi/stri...
1/3 Keksposé is going proxyless! You can now access your #Strimzi based #ApacheKafka cluster from your local computer through port-forwarding without creating any Pods and deploying a Kafka proxy inside your Kubernetes cluster.
5/9 One of the things I regret about not doing more in #Strimzi is pluggability. In the Java-based world, plugins are pretty easy to handle. And I think well-thought-through pluggable interfaces give open source projects a way to spread the maintenance and overhead efforts.
4/4 PS: If you are a Strimzi user, make sure to check out the CVE-2025-66623 and update to #Strimzi 0.49.1 if needed: github.com/strimzi/stri... 😉
1/4 A few weeks ago, I noticed that one of the #Strimzi refactorings that was done earlier this year did not have good unit test coverage, and I made a note about it in my TODO list. It was sitting there for some time as a very minor, unimportant issue.
1/2 We have just released #Strimzi 0.49.1. Apart from various smaller bug fixes and minor improvements, this release also fixes ⚠️ CVE-2025-66623. This CVE affects Strimzi versions from 0.47.0 up to 0.49.0.
Screenshot with Strimzi GitHub community pulse for November
Not exactly a busy month for #Strimzi. But we managed to get out the 0.49.0 release with the new v1 API. I guess that counts as progress ...
This release is way more important than it sounds. It sets #Strimzi on the path to the 1.0.0 release in H1/2026. It cost me two months of my life and a lot of commitment under difficult work circumstances ... so 🤞fingers crossed it works 😰
#Strimzi 0.49.0 is out! 🎉
⚠️ This release contains many important changes (including backwards compatibility impact), deprecations, and removals. Make sure to watch the What's new video and read the release notes carefully before upgrading!
➡️ github.com/strimzi/stri...
🎦 youtu.be/aIGZD8lk6vc
If you are curious about what is coming in #Strimzi 0.49.0, want to learn more about the #Strimzi v1 CRD API, and the plans for our 1.0.0 release, I prepared a few short videos to give you a preview of what to expect ...
If you use #Strimzi for local #ApacheKafka development with Minikube or Kind, Keksposé is the perfect tool for exposing your Kafka cluster locally and making local application development easy. If that sounds useful, go and try it out: github.com/scholzj/keks...
2/2 But at least I now opened the first PR and proposal for the #Strimzi v1 CRD API, which is one of the key prerequisites: github.com/strimzi/prop... ... so fingers crossed 🤞 we will get there one day. (And yes, I'm intentionally not saying anything about 2026 🫣)
1/2 In December of 2023, I wrote a blog post about our progress towards #Strimzi 1.0.0: strimzi.io/blog/2023/12.... I said there that it is unlikely to happen in 2024. Sadly, I can now say that it will not happen in 2025 either. 😞
2/3 I would recommend it to anyone who feels "dead and empty" at work 😉. It helped me to recover my energy and start looking forward to getting back to work on #Strimzi. Unfortunately, that might not be completely straightforward due to some internal changes at Red Hat / IBM.
3/3 We added support for custom authentication mechanisms. Thanks to that, you can now use Amazon MSK IAM authentication as well as any other proprietary/custom authentication mechanism used by your Kafka provider. You can look forward to it in #Strimzi 0.48!
1/3 Support for Amazon MSK IAM authentication (github.com/strimzi/stri...) was one of the #Strimzi feature requests with most 👍 reactions. But for an open source project like Strimzi, it is not easy to directly support proprietary features like this.
I wanted to test #Strimzi authentication with SASL AWS_MSK_IAM against #AmazonMSK. But after an hour of trying to setup an MSK cluster that I can access from my home lab I gave up. I guess either I'm getting old or AWS UX is even worse than it used to be. 🙄
2/2 I recently did a short survey among the #Strimzi users. And in my new blog post, I share the results, as well as the pros and cons of the various methods: strimzi.io/blog/2025/08...
1/2 How do you get Strimzi container images? Do you pull them directly from the #Strimzi container registry? Do you keep copies of the containers in your own registry? Or do you build Strimzi from source? Each approach has some (dis)advantages and potential risks.
