The deployment method shown in this guide relies on If you'd like to change the number of bookies, brokers, or ZooKeeper nodes in your Pulsar cluster, modify the As an example, we'll create a new GKE cluster for Kubernetes version By default, bookies will run on all the machines that have locally attached SSD disks. This section guides you through every step of installing and running Apache Pulsar with Helm on Kubernetes quickly, including the following sections: Install the Apache Pulsar on Kubernetes using Helm Start and stop Apache Pulsar Create topics using pulsar-admin It is built using the Now you can use the CRDs provide by Pulsar Operator to deploy your Pulsar Cluster.which defines pulsar cluster zookeeper, bookkeeper, broker, proxy components configurationClone project to the kubernetes master node(project must in GOPATH): Pulsar on Amazon Web Services You can run Kubernetes on Amazon Web Services (AWS) in a variety of ways.
but that will change as you begin deploying Pulsar components using Create SSD disk mount points on the VMs using this script:Now that you've set up a Kubernetes cluster, either on In that package, there are different sets of resource definitions for different environments.Wait until all three ZooKeeper server pods are up and have the status This step may take several minutes, as Kubernetes needs to download the Docker image on the VMs.For the sake of reference, that job runs the following command on an ephemeral pod:Once cluster metadata has been successfully initialized, you can then deploy the bookies, brokers, monitoring stack (You can check on the status of the pods for these components either in the Kubernetes Dashboard or using Once all of the components are up and running, you'll need to create at least one Pulsar tenant and at least one namespace.You can create properties and namespaces (and perform any other administrative tasks) using the Now that you have a namespace and tenant set up, you can move on to Now that a tenant and namespace have been created, you can begin experimenting with your running Pulsar cluster. Now you can navigate to You can find detailed instructions for setting up a Kubernetes cluster on AWS When you create a cluster using those instructions, your Pulsar can be deployed on a custom, non-GKE Kubernetes cluster as well. Pulsar Operator is to manage Pulsar service instances deployed on the Kubernetes cluster.
The operator also deploys a pod that runs the CRD control loop.
At first your local cluster will be empty, Clone the project on your Kubernetes cluster master node: You can find detailed instructions for setting up a Kubernetes cluster on AWS here. GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together. You can find detailed instructions for setting up a Kubernetes cluster on AWS here. For those looking to configure and install a Pulsar cluster on Kubernetes for production usage, you should follow the complete Installation Guide. Quick Start Deploy Pulsar Operator.
pulsar operator creates/configures/manages pulsar clusters atop Kubernetes Pulsar Operator Overview. For those looking to get up and running with these charts as fast as possible, in a non-production use case, we provide a quick start guide for Proof of Concept (PoC) deployments. A very simple way that was recently introducedinvolves using the Kubernetes Operations(kops) tool. Use Git or checkout with SVN using the web URL.