For K8s Should we use something like this
https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/network_filters/kafka_broker_filter#config-network-filters-kafka-broker
A pulsar filter in envoy would be great!
On Sat, 28 Aug 2021 at 23:10, Enrico Olivelli wrote:
> Joe,
> Thanks for
Joe,
Thanks for sharing your knowledge
Il Sab 28 Ago 2021, 18:34 Joe F ha scritto:
>
> To give some history and context, Pulsar proxy was meant to be a barebones
> TCP proxy when it was built. It's sole reason to exist was to forward
> network traffic to the right host. Discovery/authn/z was
To give some history and context, Pulsar proxy was meant to be a barebones
TCP proxy when it was built. It's sole reason to exist was to forward
network traffic to the right host. Discovery/authn/z was a dependency .
The way it came around, it was for a narrow use case (and it was not for
k8s),
+1 Thanks for your proposal, Enrico.
I completely agree that the Pulsar Proxy is an integral component in a
Pulsar cluster running on k8s. Further, considering that the proxy
interacts with clients as if it were a broker and that we already support
protocol handlers in the broker, I think it is a
Hello,
Currently we have the ability to add Protocol Handlers to the Pulsar
Broker, this is great, because you can add your code that uses internal
Pulsar APIs and implement your own protocols.
When you run Pulsar in k8s (and this is happening more and more) you need
to run the Pulsar proxy.
The P
