Pulsar, Heron and Apache BookKeeper on GCP cluster using Kubernetes
/
For quite some time, I have been playing with Big Data technology softwares. Specifically, I was looking for an end-to-end real-time solution for messaging, compute and streaming storage using lesser number of components and still being able to achieve Enterprise grade workloads. I have tried a variety of technology choices. Each one brought its own ecosystem and tooling components into the equation. Eventually, the end-to-end solution grew bigger and involved a lot of components.
Over the weekend, I was playing with Pulsar (incubating), Heron (incubating) and Apache BookKeeper projects. I was trying to use them for an end-to-end real time solution. Pulsar takes care of Data Ingestion. Heron takes care of Compute. BookKeeper takes care of Storage. I tried to deploy them into Google Cloud Platform (GCP) using Kubernetes. Finally, I got something working! I was able to submit a DAG (Topology) and run it.
At last, IMO, I think I have got something working which is an Enterprise grade end-to-end real time solution for messaging, compute and storage with lesser number of components. In this blog post, I am going to share that end-user experience.
This experiment was done in a Mac (macOS Sierra, version 10.12.13). The spec of my Mac is as follows:
$ pwd /Users/arivolitirouvingadame $ uname -a Darwin Arivolis-MacBook-Pro.local 16.4.0 Darwin Kernel Version 16.4.0: Thu Dec 22 22:53:21 PST 2016; root:xnu-3789.4
PRE-REQUISITES:
- Install Google SDK in your Mac.
- Install Google components like gsutil and kubectl in your Mac.
- Google Cloud Platform steps
- Create a sample project in Google Cloud Platform (GCP).
- Activate Compute Engine.
- Activate Container Engine.
INSTALLATION STEPS:
- Create Storage bucket. Associate it with the project.
- Create IAM policies.
- Install Apache BookKeeper, Pulsar and Heron softwares using kubectl.
1. INSTALL GOOGLE SDK IN YOUR MAC
Download the appropriate google-cloud-sdk tar zip from the Google site. In this experiment, the required file google-cloud-sdk-169.0.0-darwin-x86_64.tar.gz was downloaded.
$ pwd /Users/arivolitirouvingadame/Dev $ ls -ltr total 27016 r--r--@ 1 arivolitirouvingadamestaff13820245 Sep2 12:11 google-cloud-sdk-169.0.0x86_64.tar.gz
Untar google-cloud-sdk-169.0.0-darwin-x86_64.tar.gz. This would create a folder called google-cloud-sdk.
$ cd google-cloud-sdk $ pwd /Users/arivolitirouvingadame/Dev/google-cloud-sdk Arivolis-MacBook-Pro:google-cloud-sdk arivolitirouvingadame$ ls -ltr total 464 r--r-- 1 arivolitirouvingadame staff 31 Aug 28 05:13 path.zsh.inc r--r-- 1 arivolitirouvingadame staff 1210 Aug 28 05:13 path.fish.inc r--r-- 1 arivolitirouvingadame staff 308 Aug 28 05:13 path.bash.inc xr-x 1 arivolitirouvingadame staff 3701 Aug 28 05:13 install.sh xr-x 1 arivolitirouvingadame staff 1581 Aug 28 05:13 install.bat r--r-- 1 arivolitirouvingadame staff 2083 Aug 28 05:13 completion.zsh.inc r--r-- 1 arivolitirouvingadame staff 2734 Aug 28 05:13 completion.bash.inc r--r-- 1 arivolitirouvingadame staff 190880 Aug 28 05:13 RELEASE_NOTES r--r-- 1 arivolitirouvingadame staff 673 Aug 28 05:13 README r--r-- 1 arivolitirouvingadame staff 980 Aug 28 05:13 LICENSE r--r-- 1 arivolitirouvingadame staff 8 Aug 28 05:13 VERSION drwxr-xr-x 3 arivolitirouvingadame staff 102 Aug 28 05:19 rpm drwxr-xr-x 5 arivolitirouvingadame staff 170 Aug 28 05:19 platform drwxr-xr-x 3 arivolitirouvingadame staff 102 Aug 28 05:19 deb r--r-- 1 arivolitirouvingadame staff 40 Sep 3 18:59 properties drwxr-xr-x 11 arivolitirouvingadame staff 374 Sep 3 19:09 bin drwxr-xr-x 8 arivolitirouvingadame staff 272 Sep 3 19:09 lib Arivolis-MacBook-Pro:google-cloud-sdk arivolitirouvingadame$ gcloud init Welcome! This command will take you through the configuration of gcloud. Settings from your current configuration [default] are: compute: zone: us-central1-a core: account: arivolit@gmail.com disable_usage_reporting: 'False' project: sample-heron-project-1 Pick configuration to use: [1] Re-initialize this configuration [default] with new settings [2] Create a new configuration Please enter your numeric choice: 1 Your current configuration has been set to: [default] You can skip diagnostics next time by using the following flag: gcloud init --skip-diagnostics Network diagnostic detects and fixes local network connection issues. Checking network connection... .done. Reachability Check passed. Network diagnostic (1/1 checks) passed. Choose the account you would like to use to perform operations for this configuration: [1] arivolit@gmail.com [2] Log in with a new account Please enter your numeric choice: 1 You are logged in as: [arivolit@gmail.com]. Pick cloud project to use: [1] example-heron-project-1 [2] sample-heron-project-1 [3] sample-project-cluster1 [4] Create a new project Please enter numeric choice or text value (must exactly match list item): 2 Your current project has been set to: [sample-heron-project-1]. Do you want to configure Google Compute Engine (https://cloud.google.com/compute) settings (Y/n)? n Your Google Cloud SDK is configured and ready to use! * Commands that require authentication will use arivolit@gmail.com by default * Commands will reference project `sample-heron-project-1` by default Run `gcloud help config` to learn how to change individual settings This gcloud configuration is called [default]. You can create additional configurations if you work with multiple accounts and/or projects. Run `gcloud topic configurations` to learn more. Some things to try next: * Run `gcloud --help` to see the Cloud Platform services you can interact with. And run `gcloud help COMMAND` to get help on any gcloud command. * Run `gcloud topic -h` to learn about advanced features of the SDK like arg files and output formatting Arivolis-MacBook-Pro:google-cloud-sdk arivolitirouvingadame$
Run install.sh script.
$ ./install.sh Welcome to the Google Cloud SDK! To help improve the quality of this product, we collect anonymized usage data and anonymized stacktraces when crashes are encountered; additional information is available at <https://cloud.google.com/sdk/usage-statistics>. You may choose to opt out of this collection now (by choosing 'N' at the below prompt), or at any time in the future by running the following command: gcloud config set disable_usage_reporting true Do you want to help improve the Google Cloud SDK (Y/n)? Y Your current Cloud SDK version is: 169.0.0 The latest available version is: 169.0.0
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Components │ ├───────────────┬──────────────────────────────────────────────────────┬──────────────────────────┬───────────┤ │ Status│ Name │ ID│ Size │ ├───────────────┼──────────────────────────────────────────────────────┼──────────────────────────┼───────────┤ │ Not Installed │ App Engine Go Extensions │ app-engine-go│ 97.7 MiB │ │ Not Installed │ Cloud Bigtable Command Line Tool │ cbt│ 4.0 MiB │ │ Not Installed │ Cloud Bigtable Emulator│ bigtable │ 3.5 MiB │ │ Not Installed │ Cloud Datalab Command Line Tool│ datalab│ < 1 MiB │ │ Not Installed │ Cloud Datastore Emulator │ cloud-datastore-emulator │ 15.4 MiB │ │ Not Installed │ Cloud Datastore Emulator (Legacy) │ gcd-emulator │ 38.1 MiB │ │ Not Installed │ Cloud Pub/Sub Emulator │ pubsub-emulator│ 33.2 MiB │ │ Not Installed │ Emulator Reverse Proxy │ emulator-reverse-proxy │ 14.5 MiB │ │ Not Installed │ Google Container Local Builder │ container-builder-local│ 3.7 MiB │ │ Not Installed │ Google Container Registry's Docker credential helper │ docker-credential-gcr│ 2.2 MiB │ │ Not Installed │ gcloud Alpha Commands│ alpha│ < 1 MiB │ │ Not Installed │ gcloud Beta Commands │ beta │ < 1 MiB │ │ Not Installed │ gcloud app Java Extensions │ app-engine-java│ 128.1 MiB │ │ Not Installed │ gcloud app PHP Extensions (Mac OS X) │ app-engine-php-darwin│ 21.9 MiB │ │ Not Installed │ gcloud app Python Extensions │ app-engine-python│ 6.5 MiB │ │ Not Installed │ kubectl │ kubectl│ 15.9 MiB │ │ Installed │ BigQuery Command Line Tool │ bq │ < 1 MiB │ │ Installed │ Cloud SDK Core Libraries │ core │ 6.7 MiB │ │ Installed │ Cloud Storage Command Line Tool│ gsutil │ 3.0 MiB │ │ Installed │ Default set of gcloud commands │ gcloud │ │ └───────────────┴──────────────────────────────────────────────────────┴──────────────────────────┴───────────┘
To install or remove components at your current SDK version [169.0.0], run: $ gcloud components install COMPONENT_ID $ gcloud components remove COMPONENT_ID To update your SDK installation to the latest version [169.0.0], run: $ gcloud components update Modify profile to update your $PATH and enable shell command completion? Do you want to continue (Y/n)? Y The Google Cloud SDK installer will now prompt you to update an rc file to bring the Google Cloud CLIs into your environment. Enter a path to an rc file to update, or leave blank to use [/Users/arivolitirouvingadame/.bash_profile]: No changes necessary for [/Users/arivolitirouvingadame/.bash_profile]. For more information on how to get started, please visit: https://cloud.google.com/sdk/docs/quickstarts
INSTALL COMPONENT kubectl
Note: Typically, it is a good idea to go to your home directory and install any component. It is not a good idea to install components from within the google-cloud-sdk directory.
$ cd $ gcloud components install kubectl Your current Cloud SDK version is: 169.0.0 Installing components from version: 169.0.0 ┌─────────────────────────────────────────────────┐ │ These components will be installed. │ ├────────────────────────────┬─────────┬──────────┤ │ Name│ Version │ Size │ ├────────────────────────────┼─────────┼──────────┤ │ kubectl│ │ │ │ kubectl (Mac OS X, x86_64) │ 1.7.4 │ 15.9 MiB │ └────────────────────────────┴─────────┴──────────┘ For the latest full release notes, please visit: https://cloud.google.com/sdk/release_notes Do you want to continue (Y/n)? Y
╔════════════════════════════════════════════════════════════╗ ╠═ Creating update staging area ═╣ ╚════════════════════════════════════════════════════════════╝ ╔════════════════════════════════════════════════════════════╗ ╠═ Installing: kubectl═╣ ╚════════════════════════════════════════════════════════════╝ ╔════════════════════════════════════════════════════════════╗ ╠═ Installing: kubectl (Mac OS X, x86_64) ═╣ ╚════════════════════════════════════════════════════════════╝ ╔════════════════════════════════════════════════════════════╗ ╠═ Creating backup and activating new installation ═╣ ╚════════════════════════════════════════════════════════════╝ Performing post processing steps ..done. Update done!
$ gcloud components list Your current Cloud SDK version is: 169.0.0 The latest available version is: 169.0.0
┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Components │ ├───────────────┬──────────────────────────────────────────────────────┬──────────────────────────┬───────────┤ │ Status│ Name │ ID│ Size │ ├───────────────┼──────────────────────────────────────────────────────┼──────────────────────────┼───────────┤ │ Not Installed │ App Engine Go Extensions │ app-engine-go│ 97.7 MiB │ │ Not Installed │ Cloud Bigtable Command Line Tool │ cbt│ 4.0 MiB │ │ Not Installed │ Cloud Bigtable Emulator│ bigtable │ 3.5 MiB │ │ Not Installed │ Cloud Datalab Command Line Tool│ datalab│ < 1 MiB │ │ Not Installed │ Cloud Datastore Emulator │ cloud-datastore-emulator │ 15.4 MiB │ │ Not Installed │ Cloud Datastore Emulator (Legacy) │ gcd-emulator │ 38.1 MiB │ │ Not Installed │ Cloud Pub/Sub Emulator │ pubsub-emulator│ 33.2 MiB │ │ Not Installed │ Emulator Reverse Proxy │ emulator-reverse-proxy │ 14.5 MiB │ │ Not Installed │ Google Container Local Builder │ container-builder-local│ 3.7 MiB │ │ Not Installed │ Google Container Registry's Docker credential helper │ docker-credential-gcr│ 2.2 MiB │ │ Not Installed │ gcloud Alpha Commands│ alpha│ < 1 MiB │ │ Not Installed │ gcloud Beta Commands │ beta │ < 1 MiB │ │ Not Installed │ gcloud app Java Extensions │ app-engine-java│ 128.1 MiB │ │ Not Installed │ gcloud app PHP Extensions (Mac OS X) │ app-engine-php-darwin│ 21.9 MiB │ │ Not Installed │ gcloud app Python Extensions │ app-engine-python│ 6.5 MiB │ │ Installed │ BigQuery Command Line Tool │ bq │ < 1 MiB │ │ Installed │ Cloud SDK Core Libraries │ core │ 6.7 MiB │ │ Installed │ Cloud Storage Command Line Tool│ gsutil │ 3.0 MiB │ │ Installed │ Default set of gcloud commands │ gcloud │ │ │ Installed │ kubectl│ kubectl│ 15.9 MiB │ └───────────────┴──────────────────────────────────────────────────────┴──────────────────────────┴───────────┘
To install or remove components at your current SDK version [169.0.0], run: $ gcloud components install COMPONENT_ID $ gcloud components remove COMPONENT_ID To update your SDK installation to the latest version [169.0.0], run: $ gcloud components update
Now, kubectl component has been installed!
PRE-REQS: Google Cloud Platform steps
- Create a sample project in Google Cloud Platform (GCP).
- Activate Compute Engine.
- Activate Container Engine.
Create a sample project in Google Cloud Platform (GCP)
Go to GCP console and create a sample project. Lets call it example-heron-project-1. The Project name and Project ID values are example-heron-project-1.
Activate Compute Engine
Select the project created in the previous step example-heron-project-1. Click on Compute Engine in GCP console. This would activate Compute Engine for the project.
Now the Compute Engine has been activated for our project!
Activate Container Engine
For the project example-heron-project-1, click on Container Engine in GCP console. This would activate Container Engine for the project.
Now the Container Engine has been activated for our project!
INITIALIZE PROJECT via gcloud
$ cd google-cloud-sdk $ gcloud init Welcome! This command will take you through the configuration of gcloud. Settings from your current configuration [default] are: compute: zone: us-central1-a core: account: arivolit@gmail.com disable_usage_reporting: 'False' project: sample-heron-project-1 Pick configuration to use: [1] Re-initialize this configuration [default] with new settings [2] Create a new configuration Please enter your numeric choice: 1 Your current configuration has been set to: [default] You can skip diagnostics next time by using the following flag: gcloud init --skip-diagnostics Network diagnostic detects and fixes local network connection issues. Checking network connection .done. Reachability Check passed. Network diagnostic (1/1 checks) passed. Choose the account you would like to use to perform operations for this configuration: [1] arivolit@gmail.com [2] Log in with a new account Please enter your numeric choice: 1 You are logged in as: [arivolit@gmail.com]. Pick cloud project to use: [1] example-heron-project-1 [2] sample-heron-project-1 [3] sample-project-cluster1 [4] Create a new project Please enter numeric choice or text value (must exactly match list item): 2 Your current project has been set to: [sample-heron-project-1]. Do you want to configure Google Compute Engine (https://cloud.google.com/compute) settings (Y/n)? n Your Google Cloud SDK is configured and ready to use! * Commands that require authentication will use arivolit@gmail.com by default * Commands will reference project `sample-heron-project-1` by default Run `gcloud help config` to learn how to change individual settings This gcloud configuration is called [default]. You can create additional configurations if you work with multiple accounts and/or projects. Run `gcloud topic configurations` to learn more. Some things to try next: * Run `gcloud --help` to see the Cloud Platform services you can interact with. And run `gcloud help COMMAND` to get help on any gcloud command. * Run `gcloud topic -h` to learn about advanced features of the SDK like arg files and output formatting Arivolis-MacBook-Pro:google-cloud-sdk arivolitirouvingadame$
CREATE STORAGE BUCKET
$ gsutil mb gs://my-heron-bucket Creating gs://my-heron-bucket/... $
CREATE CONTAINER CLUSTERS
$ gcloud container clusters create sample-heron-cluster-1 --machine-type=n1-standard-8 --num-nodes=3 --cluster-version=1.7.4 Creating cluster sample-heron-cluster-1... .done. Created [https://container.googleapis.com/v1/projects/sample-heron-project-1/zones/us-central1-a/clusters/sample-heron-cluster-1]. kubeconfig entry generated for sample-heron-cluster-1. NAME ZONE MASTER_VERSIONMASTER_IP MACHINE_TYPE NODE_VERSIONNUM_NODESSTATUS sample-heron-cluster-1us-central1-a1.7.4 104.198.191.224n1-standard-81.7.4 3 RUNNING $
A cluster has been created!
Now we need to give kubectl permission to access this cluster.
GIVE kubectl PERMISSION TO ACCESS CLUSTER
$ gcloud container clusters get-credentials sample-heron-cluster-1 Fetching cluster endpoint and auth data. kubeconfig entry generated for sample-heron-cluster-1. $
Create a secret with google account service key
$ kubectl create secret generic heron-gcs-key --from-file=key.json=key.json secret "heron-gcs-key" created
Create a config map with gcs bucket name
Syntax:
kubectl create configmap heron-apiserver-config --from-literal=gcs.bucket=<my-bucket-name>
$ kubectl create configmap heron-apiserver-config --from-literal=gcs.bucket=my-heron-bucket
configmap "heron-apiserver-config" created
Create zookeeper
$ kubectl create -f https://raw.githubusercontent.com/twitter/heron/master/deploy/kubernetes/zookeeper.yaml storageclass "ssd" created poddisruptionbudget "zk-budget" created statefulset "zk" created service "zookeeper" created $ $ kubectl get pods NAME READY STATUS RESTARTS AGE zk-0 0/1 ContainerCreating 0 23s Arivolis-MacBook-Pro:~ arivolitirouvingadame$ kubectl get pods NAME READY STATUS RESTARTS AGE zk-0 0/1 ContainerCreating 0 31s $
Wait until the zookeeper container is ready and up and running. Because of the rest of the steps needs the zk to be up, it is necessary to wait for zk to be up and running here.
$ kubectl get pods NAME READY STATUS RESTARTS AGE zk-0 1/1 Running 0 1m $
Now, zookeeper is up and running!
CREATE TOOLS
$ kubectl create -f https://raw.githubusercontent.com/twitter/heron/master/deploy/kubernetes/tools.yaml deployment "heron-tracker" created service "heron-ui" created $ $ kubectl get pods NAME READY STATUSRESTARTS AGE heron-tracker-4236240521-lmbqs 0/2 ContainerCreating 017s zk-0 1/1 Running 02m
Wait until heron-tracker is Running.
$ kubectl get pods NAME READY STATUSRESTARTS AGE heron-tracker-4236240521-lmbqs 2/2 Running 059s zk-0 1/1 Running 03m $
Now, heron-tracker is up and running!
CREATE APISERVER
$ kubectl create -f https://raw.githubusercontent.com/twitter/heron/master/deploy/kubernetes/gcp/apiserver.yaml deployment "heron-apiserver" created service "heron-apiserver" created $ kubectl get pods NAME READY STATUSRESTARTS AGE heron-apiserver-1238049208-vrp5x 0/2 ContainerCreating 06s heron-tracker-4236240521-lmbqs 2/2 Running 01m zk-0 1/1 Running 03m $
Wait until heron-apiserver is Running.
$ kubectl get pods NAME READY STATUSRESTARTS AGE heron-apiserver-1238049208-vrp5x 2/2 Running 01m heron-tracker-4236240521-lmbqs 2/2 Running 03m zk-0 1/1 Running 05m $
Now, heron-apiserver is up and running!
Launch proxy
Go to another terminal window, and launch proxy.
$ kubectl proxy Starting to serve on 127.0.0.1:8001
heron-ui Topology dashboard
Open a browser and go to http://localhost:8001/api/v1/proxy/namespaces/default/services/heron-ui:8081/topologies URL.
Here is a sample screen shot of the Topology dashboard. Since no topology has been submitted so far, the dashboard would be empty.
heron-apiserver
Now, open up a browser tab and go to http://localhost:8001/api/v1/proxy/namespaces/default/services/heron-apiserver:9000/api/v1/version URL.
Here is the expected output for the heron-apiserver request.
{
"heron.build.git.revision" : "bda9ef094864ba5f37f8a8c00306601861e61bbc",
"heron.build.git.status" : "Clean",
"heron.build.host" : "Karthikz-MacBook-Pro.local",
"heron.build.time" : "Fri Sep 1 14:26:21 PDT 2017",
"heron.build.timestamp" : "1504301237000",
"heron.build.user" : "karthikz",
"heron.build.version" : "0.15.2"
}
The next step would be to submit a Topology. For that, we need to install heron-client on my Mac.
INSTALL heron-client
The Heron releases are available here. For this exercise, I chose Darwin 0.15.2 version and downloaded heron-client from
https://github.com/twitter/heron/releases/download/0.15.2/heron-client-install-0.15.2-darwin.sh
Open up another terminal and do the following:
$ pwd /Users/arivolitirouvingadame/Downloads $ chmod 755 heron-client-install-0.15.2-darwin.sh $ ./heron-client-install-0.15.2-darwin.sh --user Heron client installer ---------------------- Uncompressing..tar xfz /Users/arivolitirouvingadame/.heron/heron-client.tar.gz -C /Users/arivolitirouvingadame/.heron . Heron is now installed! Make sure you have "/Users/arivolitirouvingadame/bin" in your path. See http://heronstreaming.io/docs/getting-started for how to use Heron. heron.build.version : '0.15.2' heron.build.time : Fri Sep 1 14:50:47 PDT 2017 heron.build.timestamp : 1504302734000 heron.build.host : Karthikz-MacBook-Pro.local heron.build.user : karthikz heron.build.git.revision : bda9ef094864ba5f37f8a8c00306601861e61bbc heron.build.git.status : Clean $ which heron /Users/arivolitirouvingadame/bin/heron $
Submit a Heron topology
Here is a sample of how to submit an ExclamationTopology job:
$ heron submit kubernetes --service-url http://localhost:8001/api/v1/proxy/namespaces/default/services/heron-apiserver:9000/ ~/.heron/examples/heron-examples.jarcom.twitter.heron.examples.WordCountTopology wc1 [2017-09-03 21:06:40 -0700] [INFO]: Launching topology: 'wc1' [2017-09-03 21:06:49 -0700] [INFO]: Successfully launched topology 'wc1' $
Note: Currently, the Topology name MUST be in Upper case. Hence, I have named my topology wc1 instead of, say WC1.
Test if the Heron topology is running successfully
Lets first verify from kubectl if the wc1 pod is up and running.
$ kubectl get pods NAME READY STATUSRESTARTS AGE wc1-0 1/1 Running 054s wc1-1 1/1 Running 054s wc1-2 1/1 Running 054s heron-apiserver-1238049208-vrp5x 2/2 Running 021m heron-tracker-4236240521-lmbqs 2/2 Running 022m zk-0 1/1 Running 025m $
Now, let us go to the dashboard and see if the Topology shows up!
Terminate a Heron topology
When you are done with your experimentation, you can clean up your topology. Here is the command for cleaning up:
$ heron kill kubernetes --service-url http://localhost:8001/api/v1/proxy/namespaces/default/services/heron-apiserver:9000/ wc1 [2017-09-03 21:10:51 -0700] [INFO]: Successfully kill topology: wc1 $ $ kubectl get pods NAME READY STATUSRESTARTS AGE wc1-0 1/1 Terminating 04m wc1-1 1/1 Terminating 04m wc1-2 1/1 Terminating 04m heron-apiserver-1238049208-vrp5x 2/2 Running 024m heron-tracker-4236240521-lmbqs 2/2 Running 026m zk-0 1/1 Running 028m $ $ kubectl get pods NAME READY STATUSRESTARTS AGE heron-apiserver-1238049208-vrp5x 2/2 Running 025m heron-tracker-4236240521-lmbqs 2/2 Running 027m zk-0 1/1 Running 029m $
REVIEW:
Disclaimer: The reviews are my own views, and not that of my employer. Please be cognizant of the fact that I am just sharing my experience here. This is not meant to hurt any sentiments of the very many Open source projects which I have learned, enjoyed and benefitted from over the years!
Pain points:
The pain points were in setting up the GCP related pre-requisites. I had some hiccups and it took a lot of time. Also, to increase the size of the cluster quota, I had to call the GCP Tech support guy. I wanted to do all the GCP related steps from CLI via gcloud. But I ran into issues and it was cumbersome. So, I ended up switching between GCP console and gcloud CLI. I did the initial part of the GCP pre-reqs from GCP console. I did the rest of the GCP pre-req steps from gcloud CLI.
Good points:
Setting up Pulsar, Heron and Apache BookKeeper was very smooth and straight forward!
Overall, it was a great experience. I was able to deploy Big Data technology softwares (Pulsar, Heron and Apache BookKeeper) in GCP as a cluster using Kubernetes, and submit a Topology via CLI from my Mac. I was able to see the results as well!