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

Expose Kafka Connect REST API to the outside world #130

Closed
scholzj opened this issue Jan 4, 2018 · 4 comments
Closed

Expose Kafka Connect REST API to the outside world #130

scholzj opened this issue Jan 4, 2018 · 4 comments

Comments

@scholzj
Copy link
Member

scholzj commented Jan 4, 2018

It should be possible to expose Kafka Connect to the outside of OpenShift / Kubernetes world.

@scholzj
Copy link
Member Author

scholzj commented Sep 10, 2020

Reviewed on 10th Sep 2020: This might still make sense after security is solved. We should keep it open for the time being.

@scholzj scholzj changed the title Expose Kafka Connect to the outside world Expose Kafka Connect REST API to the outside world May 26, 2022
@scholzj
Copy link
Member Author

scholzj commented May 26, 2022

Triaged on 26.5.2022: Strimzi provides the connector operator to completely avoid using the REST API. Also, unlike Kafka brokers, there are no advertised listeners etc. So any user can easily set up their own load balancer service, node port service, Ingress etc. on their own just as another resource together with the Connect CR. So this does not seem to be needed anymore.

@scholzj scholzj closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2022
@sokolbiba
Copy link

Is it possible to secure the Kafka Connect REST api implemented by strimzi KafkaConnect?

@scholzj
Copy link
Member Author

scholzj commented Oct 31, 2022

Is it possible to secure the Kafka Connect REST api implemented by strimzi KafkaConnect?

No, that is currently not supported.

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