Pulsar proxy
Before using the proxy, you need to configure it with the brokers addresses in the cluster. You can configure the broker URL in the proxy configuration, or the proxy to connect directly using service discovery.
It is more secure to specify a URL to connect to the brokers.
Proxy authorization requires access to ZooKeeper, so if you use these broker URLs to connect to the brokers, you need to disable authorization at the Proxy level. Brokers still authorize requests after the proxy forwards them.
You can configure the broker URLs in as follows.
The hostname in the URLs provided should be a DNS entry which points to multiple brokers or a virtual IP address, which is backed by multiple broker IP addresses, so that the proxy does not lose connectivity to Pulsar cluster if a single broker becomes unavailable.
The ports to connect to the brokers (6650 and 8080, or in the case of TLS, 6651 and 8443) should be open in the network ACLs.
Note that if you do not use functions, you do not need to configure functionWorkerWebServiceURL
.
Use service discovery
Pulsar uses for service discovery. To connect the proxy to ZooKeeper, specify the following in .
To start the proxy:
Pulsar proxy runs in the foreground by default. To stop the proxy, simply stop the process in which the proxy is running.
You can run Pulsar proxy behind some kind of load-distributing frontend, such as an HAProxy load balancer.
Once your Pulsar proxy is up and running, preferably behind a load-distributing , clients can connect to the proxy via whichever address that the frontend uses. If the address is the DNS address pulsar.cluster.default
, for example, the connection URL for clients is .