Skip to content
Discussion options

You must be logged in to vote

One alternative is to use internal ClusterIP listener and create "manually" ingresses, with a host and a path, for bootstrap and each broker, but if we want to use ingress lister, we can add new fields "path" to have a full path like hostname+path

Did you actually tried it? Does it work?

Kafka is not an HTTP protocol. That is why you need to enable TLS passthrough in your Ingress and use it only with TLS. It uses TLS-SNI to pass the connection to the right service. Similarly, the advertised listener configuration in Kafka has place for path since there is nothing like that in the Kafka protocol. So I do not think there is any place for the path on either end and this will simply not work.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@maknihamdi
Comment options

Answer selected by maknihamdi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
2 participants
Converted from issue

This discussion was converted from issue #7971 on January 25, 2023 13:44.