I get that. If Kafka decides to adopt a different solution, it might be costly for them. So yes, financially, it makes sense. But I do not think that makes it the right thing to do.

2/2 First time I see this kind of thing, so genuinely curious. But it does not seem to me like a healthy way to build a community. 🤔

1️⃣ Upgrade to Strimzi 0.49.0: youtu.be/IpR8gizh35g

2️⃣ Converting Resources: youtu.be/keM70eirDPk

3️⃣ Upgrade to Strimzi 1.0.0: youtu.be/GFXlhdDltT4

4️⃣ Timelines and Main API Changes: youtu.be/qTcv-EiUXOs

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 🫣)

3/3 So it remains to be seen what happens next. But hey, that is how things go sometimes ... 🤷‍♂️. In any case, kudos to my managers for supporting me through my time off as well as trying to resolve the new issues.

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!

2/3 It is hard to test (as it depends on Amazon AWS infrastructure) and we cannot guarantee compatibility with future versions. Also, direct support for all available proprietary authentication mechanisms like this does not really scale. So we did the next best thing.