Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timeline on supporting kafka version 3.3.1 (Kraft) #2405

Closed
Derek-Hardy opened this issue Dec 18, 2022 · 3 comments
Closed

Timeline on supporting kafka version 3.3.1 (Kraft) #2405

Derek-Hardy opened this issue Dec 18, 2022 · 3 comments
Labels
stale Issues and pull requests without any recent activity

Comments

@Derek-Hardy
Copy link

Versions

latest (v1.37.2)

Configuration

What configuration values are you using for Sarama and Kafka?

V3_2_3_0  = newKafkaVersion(3, 2, 3, 0)
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

@Derek-Hardy Derek-Hardy changed the title Kafka version support for 3.3.1 Kraft Timeline on supporting kafka version 3.3.1 (Kraft) Dec 18, 2022
@dnwe
Copy link
Collaborator

dnwe commented Dec 21, 2022

@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

@dnwe
Copy link
Collaborator

dnwe commented Dec 21, 2022

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

@github-actions
Copy link

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.

@github-actions github-actions bot added the stale Issues and pull requests without any recent activity label Jul 18, 2023
@dnwe dnwe closed this as completed Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues and pull requests without any recent activity
Projects
None yet
Development

No branches or pull requests

2 participants