Skip to content
This repository has been archived by the owner on Feb 20, 2024. It is now read-only.

Clarity on Externally exposing connect and kafka broker #628

Open
gavasv-sapiens opened this issue Nov 16, 2022 · 3 comments
Open

Clarity on Externally exposing connect and kafka broker #628

gavasv-sapiens opened this issue Nov 16, 2022 · 3 comments

Comments

@gavasv-sapiens
Copy link

Hello Community,
We are currently planning to use this helm deployments for our Dev environment. One issue that we are facing is current helms does not have ingress or external Ip load balancer for them.
Anyone with the knowledge on this can you please guide us on how to we manage to have consumer and producer onto the broker.
Any help will be appreciated.
Regards
Vishal Gavas

@OneCricketeer
Copy link

These charts are no longer maintained. Perhaps this blog can add clarity - https://strimzi.io/blog/2019/04/17/accessing-kafka-part-1/

@KamranAlektum
Copy link

@OneCricketeer
what do you mean?
is these charts deprecated! if yes which chart available there for kafka and it's assets like connect ?

@OneCricketeer
Copy link

These charts are deprecated for Confluent Operator for Kubernetes (CFK)

Kafka Connect isn't specific to Confluent, though, so you could also use Strimzi Kafka Connect CRDs

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants