You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should investigate what impact does the KIP-891 have on Strimzi. Its expected introduction seems to be currently in Kafka 4.0.0. The one area that comes to my mind with possible impact is the KafkaConnector CRD -> do we expect the version to be specified in .spec.config? Or should we have a dedicated field for it such as .spec.version? Ideally, we should clarify this before releasing Kafka 4.0.0 support as changing it later might cause backwards compatibility issues.
The text was updated successfully, but these errors were encountered:
Triaged on 9.1.2025: @mimaison mentioned that the KIP is now targeting Kafka 4.1.0. @katheris is for the .spec.version option. Let's give others more time to go through the KIP - we will go through it on the next community call.
Triaged on 23.1.2025: we agreed on having the support and it seems that having a .spec.version field could be the way. We would need a proposal for that.
We should investigate what impact does the KIP-891 have on Strimzi. Its expected introduction seems to be currently in Kafka 4.0.0. The one area that comes to my mind with possible impact is the
KafkaConnector
CRD -> do we expect the version to be specified in.spec.config
? Or should we have a dedicated field for it such as.spec.version
? Ideally, we should clarify this before releasing Kafka 4.0.0 support as changing it later might cause backwards compatibility issues.The text was updated successfully, but these errors were encountered: