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
@Derek-Hardy sure I can add the missing kafka version(s) to the matrix and the CI checks — though there's no specific requirement to match the broker version as we just use that config var to cap the maximum protocol versions, but we haven't added/implemented anything special for 3.3.x
So #2406 adds 3.3.1 constants and includes it in the fvt testing matrix — this is still using it in zookeeper mode though, I'll probably look at making an fv run that deploys it in kraft mode too, although that should only effect server-side and the client doesn't need to change its behaviour
Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the main branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.
Versions
latest (v1.37.2)
Configuration
What configuration values are you using for Sarama and Kafka?
Problem Description
What is the timeline on supporting the latest Kraft production-ready Kafka version 3.3.1?
The latest Sarama only has version variables until v3.2.3
The text was updated successfully, but these errors were encountered: