Skip to content

To make Kafka accessible from IDE on port 9093 - #223

Open
kmozaid wants to merge 3 commits into
debezium:mainfrom
kmozaid:main
Open

To make Kafka accessible from IDE on port 9093#223
kmozaid wants to merge 3 commits into
debezium:mainfrom
kmozaid:main

Conversation

@kmozaid

@kmozaid kmozaid commented May 20, 2022

Copy link
Copy Markdown

No description provided.

@jpechane

Copy link
Copy Markdown
Contributor

@kmozaid Hi, thanks for the PR

  • Is it ok to advertise endpoint that is not accessible for some of the clients?
  • WOuld it be possible to introduce the same change into all tutorial composes?

@kmozaid

kmozaid commented May 23, 2022

Copy link
Copy Markdown
Author

@kmozaid Hi, thanks for the PR

  • Is it ok to advertise endpoint that is not accessible for some of the clients?
  • WOuld it be possible to introduce the same change into all tutorial composes?

HI @jpechane

  • The endpoint EXTERNAL://localhost:9093 is advertised so that clients on docker host can access Kafka running in docker. If we specify this external endpoint then we also need to advertise endpoint for internal service like kafka connect (The endpoint CLIENT://kafka:9092 is for Kafka Connect Docker).
  • Sure, I can update other docker-compose files.

@rk3rn3r

rk3rn3r commented May 23, 2022

Copy link
Copy Markdown
Member

Quick question: Is it valuable to map to a static port? Won't this conflict with multiple containers running concurrently? Would it be possible to use random ports and map the config in the entrypoint script?
Else, we should at least mind in the docs that this can conflict and running the same container multiple times isn't supported.
wdyt @jpechane ?

Comment thread tutorial/docker-compose-postgres.yaml Outdated
@OneCricketeer

OneCricketeer commented Jul 27, 2022

Copy link
Copy Markdown

Won't this conflict with multiple containers running concurrently

Yes.

possible to use random ports and map the config in the entrypoint script

advertised.listeners needs to have a static value, albeit one could be dynamically generated, but then how would compose or the Dockerfile expose that random value without defining it statically in those configs?

@kmozaid

kmozaid commented Feb 10, 2023

Copy link
Copy Markdown
Author

@OneCricketeer and @jpechane Sorry for the very late update on this PR, please review once again, I have made the required changes.

@Naros

Naros commented Jan 6, 2026

Copy link
Copy Markdown
Member

❌ Developer Certificate of Origin (DCO) check failed.

Hi @kmozaid, please sign off all commits with:

git commit -s

If pull request commits are not signed off, the pull request cannot be merged. For more information about why this is required, please see our blog about contribution requirement changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants