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

more test for MSK/Kafka #14072

Closed
lmatz opened this issue Dec 20, 2023 · 2 comments
Closed

more test for MSK/Kafka #14072

lmatz opened this issue Dec 20, 2023 · 2 comments

Comments

@lmatz
Copy link
Contributor

lmatz commented Dec 20, 2023

quote from @twocode:

I feel like we only tested the easy path with MSK (at least from our documentation). We didn’t test our the complex part, for example the public access has the most complex config of network, security groups, server setting and ACL rules. It’s not well documented.

The current MSK documentation: https://docs.risingwave.com/docs/current/connector-amazon-msk/

@github-actions github-actions bot added this to the release-1.6 milestone Dec 20, 2023
@lmatz lmatz removed this from the release-1.6 milestone Jan 9, 2024
Copy link
Contributor

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.

@neverchanje
Copy link
Contributor

The only feature that I am aware but unsupported now is "ssh tunnel", which allow clients outside AWS to connect to MSK through a jumpserver.
Leaving it aside, I am unaware of other lacking features for Kafka source. A difference between MSK and self-hosted Kafka is AWS IAM auth, which has recently been supported.
In general, I don't agree with the idea that "we only tested the easy path with MSK".

@lmatz lmatz closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants