Skip to content

Advertise per-pod external listener when external access is enabled (3.8.1) - #56

Closed
al-masood wants to merge 1 commit into
release-3.8.1from
kafka-external-3.8.1
Closed

al-masood wants to merge 1 commit into
release-3.8.1from
kafka-external-3.8.1

Conversation

@al-masood

Copy link
Copy Markdown
Member

When external access is enabled, the KubeDB Kafka operator mounts external-listeners.properties into the temp config dir, with one <pod-name>=EXTERNAL://<address>:<port> line per broker. The kafka-init setup.sh used by 4.x already appends the pod's line to advertised.listeners. This ports the same block to the entrypoint baked into the 3.x images, so external access can work on 3.x as well.

  • If the file is not mounted, startup is unchanged.
  • If the file is mounted but has no line for the pod, the broker exits with an error instead of starting without an external address.

The same commit is opened against release-3.5.2, 3.6.1, 3.7.2, 3.8.1 and 3.9.0.

Testing: only bash -n was run. No image has been built and no broker has been started with this change yet.

Signed-off-by: Abdullah Al Masood <masood@appscode.com>
@al-masood al-masood closed this Nov 17, 2026
@al-masood
al-masood deleted the kafka-external-3.8.1 branch November 17, 2026 05:08
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.

1 participant