Getting Started
The initial default configuration provides a basic Pulsar messaging cluster that consists of zookeepers, bookies, brokers, and proxies. In addition, it consists of recovery and toolset pods to handle administrative actions following the Apache Pulsar helm example. A Kubernetes service is used to provide in-cluster DNS-based access through the proxies. The corresponding Client TCP URL is available on your capability details card. Install defaults to auth disabled and include a namespace public/default that can be used for immediate pub-sub scenarios.
For more information about how to set up and administer your cluster, see the Apache Pulsar documentation.