This is an automated email from the ASF dual-hosted git repository.
liuyu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 947072f3fb5 [fix][doc] Changed in the IBM login url (#440)
947072f3fb5 is described below
commit 947072f3fb5ebd066e42d29197eac85a5052973b
Author: Rakesh Soni <[email protected]>
AuthorDate: Mon Mar 13 07:20:33 2023 +0530
[fix][doc] Changed in the IBM login url (#440)
---
.../version-2.10.x => docs}/deploy-ibm.md | 29 +--
docs/install-deploy-upgrade-landing.md | 1 +
sidebars.json | 1 +
versioned_docs/version-2.10.x/deploy-ibm.md | 25 +--
versioned_docs/version-2.11.x/deploy-ibm.md | 237 ++++++++++++++++++++-
versioned_docs/version-2.9.x/deploy-ibm.md | 26 +--
6 files changed, 277 insertions(+), 42 deletions(-)
diff --git a/versioned_docs/version-2.10.x/deploy-ibm.md b/docs/deploy-ibm.md
similarity index 81%
copy from versioned_docs/version-2.10.x/deploy-ibm.md
copy to docs/deploy-ibm.md
index 61104c99791..ef7253b18f7 100644
--- a/versioned_docs/version-2.10.x/deploy-ibm.md
+++ b/docs/deploy-ibm.md
@@ -7,10 +7,11 @@ original_id: deploy-ibm
:::tip
-This tutorial uses Apache Pulsar 2.9.3 as an example. If you want to upgrade
Pulsar version, follow the instructions in [Helm Upgrade
Guide](helm-upgrade.md).
+This tutorial uses Apache Pulsar 2.9.3 as an example. If you want to upgrade
Pulsar version, follow the instructions in [Helm Upgrade
Guide](https://pulsar.apache.org/docs/2.10.x/helm-upgrade/).
:::
+
Deploying a Pulsar cluster on IBM cloud consists of the following steps:
1. [Create VM on IBM Cloud.](#create-vm-on-ibm-cloud)
@@ -19,9 +20,9 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
4. [Verify the deployment.](#run-kubectl-commands-to-verify-the-deployment)
-#### Create VM on IBM Cloud
+## 1. Create VM on IBM Cloud
-1. Go to [IBM Cloud]( https://cloud.ibm.com/login) and login with your
credentials.
+1. Go to [IBM Cloud](
https://cloud.ibm.com/?cm_sp=freelancer-_-pulsar-iks-_-cta) and login with
your credentials.
2. Search for Virtual Server.
3. Select Virtual Server for Classic.
@@ -66,11 +67,11 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-13. Check the devices list, click on the menu option on the same page.
+13. Check the devices list, and click on the menu option on the same page.
-#### Create Kubernetes Cluster on IBM
+## 2. Create Kubernetes Cluster on IBM
1. Search for the Kubernetes services
@@ -107,7 +108,7 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-9. Check the created cluster list through clicking on the clusters options
+9. Check the created cluster list by clicking on the clusters options.
@@ -115,7 +116,7 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-## Step 3: Prepare VM for connecting to Kubernetes cluster and deploy Pulsar
Helm chart on Kubernetes cluster.
+## 3. Prepare VM for connecting to Kubernetes cluster and deploy Pulsar Helm
chart on Kubernetes cluster.
**Prerequisites**
1. Install [IBM Cloud
CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli) and connect
to Kubernetes master node.
@@ -162,12 +163,12 @@ Output
> Now we are able to run commands of kubectl.
-## Verify the deployment
+## 4. Verify the deployment
Make sure all the pods of Pulsar are running. Get the service URL and broker
URL for publishing and consuming the messages.
-> [Installation of Pulsar helm in minikube cluster](getting-started-helm.md)
this document is for minikube cluster we are taking reference from that.
+> [Installation of Pulsar helm in minikube
cluster](https://pulsar.apache.org/docs/getting-started-helm/) this document
is for minikube cluster we are taking reference from that.
1. Add Pulsar chart repo
@@ -187,11 +188,11 @@ git clone https://github.com/apache/pulsar-helm-chart
cd pulsar-helm-chart
```
-3. Run the script`prepare_helm_release.sh`to create secrets required for
installing the Apache Pulsar Helm chart. The username`pulsar`and
password`pulsar`are used for logging into the Grafana dashboard and Pulsar
Manager.
+3. Run the script `prepare_helm_release.sh` to create secrets required for
installing the Apache Pulsar Helm chart. The username `pulsar` and password
`pulsar` are used for logging into the Grafana dashboard and Pulsar Manager.
:::note
-When running the script, you can use`-n`to specify the Kubernetes namespace
where the Pulsar Helm chart is installed,`-k`to define the Pulsar Helm release
name, and`-c`to create the Kubernetes namespace. For more information about the
script, run `./scripts/pulsar/prepare_helm_release.sh --help`.
+When running the script, you can use `-n` to specify the Kubernetes namespace
where the Pulsar Helm chart is installed,`-k`to define the Pulsar Helm release
name, and `-c` to create the Kubernetes namespace. For more information about
the script, run `./scripts/pulsar/prepare_helm_release.sh --help`.
:::
@@ -210,7 +211,7 @@ helm install --values examples/values-minikube.yaml --set
initialize=true asia a
:::note
-You need to specify`--set initialize=true`when installing Pulsar the first
time. This command installs and starts Apache Pulsar.
+You need to specify `--set initialize=true` when installing Pulsar the first
time. This command installs and starts Apache Pulsar.
:::
@@ -222,7 +223,7 @@ Output
```bash
kubectl get pods
```
-If all pods start up successfully, you can see that `STATUS`is changed
to`Running`or`Completed`.
+If all pods start up successfully, you can see that `STATUS` is changed to
`Running` or `Completed`.
Output
@@ -242,4 +243,4 @@ The output shows both `services URL` and `broker URL`.
Proxy external IPs are the ports changed just now:
- Service URL port is 80.
- Broker URL port is 6650. This is default.
-If you execute all the commands successfully, you can use the Pulsar client to
connect to ?? clusters and produce and consume messages through proxy external
IPs.
+If you execute all the commands successfully, you can use the Pulsar client to
connect to clusters and produce and consume messages through proxy external
IPs.
diff --git a/docs/install-deploy-upgrade-landing.md
b/docs/install-deploy-upgrade-landing.md
index b7fe6c1455d..6237940e52b 100644
--- a/docs/install-deploy-upgrade-landing.md
+++ b/docs/install-deploy-upgrade-landing.md
@@ -15,6 +15,7 @@ Any developer can install, deploy, and upgrade Apache Pulsar
in a few simple ste
- [Upgrade Pulsar Helm release](helm-upgrade.md)
+- [Deploy a Pulsar cluster on IBM Cloud](deploy-ibm.md)
diff --git a/sidebars.json b/sidebars.json
index f3a17c527f2..17e48e6f928 100644
--- a/sidebars.json
+++ b/sidebars.json
@@ -217,6 +217,7 @@
},
"items": [
"deploy-aws",
+ "deploy-ibm",
{
"type": "category",
"label": "Kubernetes",
diff --git a/versioned_docs/version-2.10.x/deploy-ibm.md
b/versioned_docs/version-2.10.x/deploy-ibm.md
index 61104c99791..e41dea0e924 100644
--- a/versioned_docs/version-2.10.x/deploy-ibm.md
+++ b/versioned_docs/version-2.10.x/deploy-ibm.md
@@ -11,6 +11,7 @@ This tutorial uses Apache Pulsar 2.9.3 as an example. If you
want to upgrade Pul
:::
+
Deploying a Pulsar cluster on IBM cloud consists of the following steps:
1. [Create VM on IBM Cloud.](#create-vm-on-ibm-cloud)
@@ -19,9 +20,9 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
4. [Verify the deployment.](#run-kubectl-commands-to-verify-the-deployment)
-#### Create VM on IBM Cloud
+## 1. Create VM on IBM Cloud
-1. Go to [IBM Cloud]( https://cloud.ibm.com/login) and login with your
credentials.
+1. Go to [IBM Cloud](
https://cloud.ibm.com/?cm_sp=freelancer-_-pulsar-iks-_-cta) and login with
your credentials.
2. Search for Virtual Server.
3. Select Virtual Server for Classic.
@@ -66,11 +67,11 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-13. Check the devices list, click on the menu option on the same page.
+13. Check the devices list, and click on the menu option on the same page.
-#### Create Kubernetes Cluster on IBM
+## 2. Create Kubernetes Cluster on IBM
1. Search for the Kubernetes services
@@ -107,7 +108,7 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-9. Check the created cluster list through clicking on the clusters options
+9. Check the created cluster list by clicking on the clusters options.
@@ -115,7 +116,7 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-## Step 3: Prepare VM for connecting to Kubernetes cluster and deploy Pulsar
Helm chart on Kubernetes cluster.
+## 3. Prepare VM for connecting to Kubernetes cluster and deploy Pulsar Helm
chart on Kubernetes cluster.
**Prerequisites**
1. Install [IBM Cloud
CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli) and connect
to Kubernetes master node.
@@ -162,7 +163,7 @@ Output
> Now we are able to run commands of kubectl.
-## Verify the deployment
+## 4. Verify the deployment
Make sure all the pods of Pulsar are running. Get the service URL and broker
URL for publishing and consuming the messages.
@@ -187,11 +188,11 @@ git clone https://github.com/apache/pulsar-helm-chart
cd pulsar-helm-chart
```
-3. Run the script`prepare_helm_release.sh`to create secrets required for
installing the Apache Pulsar Helm chart. The username`pulsar`and
password`pulsar`are used for logging into the Grafana dashboard and Pulsar
Manager.
+3. Run the script`prepare_helm_release.sh`to create secrets required for
installing the Apache Pulsar Helm chart. The username `pulsar` and password
`pulsar` are used for logging into the Grafana dashboard and Pulsar Manager.
:::note
-When running the script, you can use`-n`to specify the Kubernetes namespace
where the Pulsar Helm chart is installed,`-k`to define the Pulsar Helm release
name, and`-c`to create the Kubernetes namespace. For more information about the
script, run `./scripts/pulsar/prepare_helm_release.sh --help`.
+When running the script, you can use `-n` to specify the Kubernetes namespace
where the Pulsar Helm chart is installed,`-k`to define the Pulsar Helm release
name, and `-c` to create the Kubernetes namespace. For more information about
the script, run `./scripts/pulsar/prepare_helm_release.sh --help`.
:::
@@ -210,7 +211,7 @@ helm install --values examples/values-minikube.yaml --set
initialize=true asia a
:::note
-You need to specify`--set initialize=true`when installing Pulsar the first
time. This command installs and starts Apache Pulsar.
+You need to specify `--set initialize=true` when installing Pulsar the first
time. This command installs and starts Apache Pulsar.
:::
@@ -222,7 +223,7 @@ Output
```bash
kubectl get pods
```
-If all pods start up successfully, you can see that `STATUS`is changed
to`Running`or`Completed`.
+If all pods start up successfully, you can see that `STATUS` is changed to
`Running` or `Completed`.
Output
@@ -242,4 +243,4 @@ The output shows both `services URL` and `broker URL`.
Proxy external IPs are the ports changed just now:
- Service URL port is 80.
- Broker URL port is 6650. This is default.
-If you execute all the commands successfully, you can use the Pulsar client to
connect to ?? clusters and produce and consume messages through proxy external
IPs.
+If you execute all the commands successfully, you can use the Pulsar client to
connect to clusters and produce and consume messages through proxy external
IPs.
diff --git a/versioned_docs/version-2.11.x/deploy-ibm.md
b/versioned_docs/version-2.11.x/deploy-ibm.md
index eadb9a7631e..ce6bfd95268 100644
--- a/versioned_docs/version-2.11.x/deploy-ibm.md
+++ b/versioned_docs/version-2.11.x/deploy-ibm.md
@@ -4,12 +4,243 @@ title: Apache Pulsar Installation on IBM Kubernetes Cluster
through Helm chart
sidebar_label: "IBM Cloud Services"
original_id: deploy-ibm
---
-# Apache Pulsar Installation on IBM Kubernetes Cluster through Helm chart
:::tip
-This tutorial uses Apache Pulsar 2.9.3 as an example. If you want to upgrade
Pulsar version, follow the instructions in [Helm Upgrade
Guide](helm-upgrade.md).
+This tutorial uses Apache Pulsar 2.9.3 as an example. If you want to upgrade
Pulsar version, follow the instructions in [Helm Upgrade
Guide](https://pulsar.apache.org/docs/2.10.x/helm-upgrade/).
:::
-[Deploying a Pulsar cluster on IBM cloud you need to Follow this
link](deploy-ibm.md)
\ No newline at end of file
+
+Deploying a Pulsar cluster on IBM cloud consists of the following steps:
+
+1. [Create VM on IBM Cloud.](#create-vm-on-ibm-cloud)
+2. [Create Kubernete cluster on IBM Cloud.](#create-kubernetes-cluster-on-ibm)
+3. [Prepare VM for connecting to Kubernetes cluster and deploy Pulsar Helm
chart on Kubernetes
cluster.](#prepare-vm-for-connecting-to-kubernetes-cluster-and-deploy-pulsar-helm-chart-on-kubernetes-cluster)
+4. [Verify the deployment.](#run-kubectl-commands-to-verify-the-deployment)
+
+
+## 1. Create VM on IBM Cloud
+
+1. Go to [IBM Cloud](
https://cloud.ibm.com/?cm_sp=freelancer-_-pulsar-iks-_-cta) and login with
your credentials.
+2. Search for Virtual Server.
+3. Select Virtual Server for Classic.
+
+
+
+4. Select the type of virtual server as selected "Public" in the image.
+ Type the host name, quantity of the machine and billing method.
+
+
+
+5. Select location value according to your region. For example: In below image
we have selected Chennai in Asia region.
+
+
+
+6. Select the profile of virtual machine.
+
+
+
+7. Select the operating system and version.
+
+
+
+8. Select network interface according to use.
+
+
+
+9. Select the security group.
+
+
+
+10. Leave rest of the things could be default. Click on the "Create" button.
+
+
+
+11. Check created VM in "Navigation Menu" -> "Resource list" Devices
+
+
+
+
+
+12. Check the detail of VM in overview
+
+
+
+13. Check the devices list, and click on the menu option on the same page.
+
+
+
+## 2. Create Kubernetes Cluster on IBM
+
+1. Search for the Kubernetes services
+
+
+
+2. Select the plan details to "Standard". Please note "Free" plan has the
limited resources, which can not fulfill the Pulsar cluster requirement.
+
+
+
+3. Select the infrastructure type we are going with the classic and also
select the Kubernetes version .
+
+
+
+4. Select location and resource group. Select single single zone or multi zone
as per your need.
+
+
+
+
+
+5. Select worker pool size and flavor (vCPU, Memory) of the worker.
+
+
+
+
+
+6. Set cluster name as you want.
+
+
+7. Leave rest of the things as we are selecting as default. You can disable
below options. Click on create and wait for provisioning of the cluster.
+
+
+
+8. After the cluster is successfully provisioned, connect to the cluster. In
order to connect click on the "Action" button then click on "Connect via CLI",
it will give you commands, copy that and run in your VM so that we can
communicate to cluster through VM. We have to configure VM for communicating to
cluster in the next steps will describe how to configure VM for that.
+
+
+
+9. Check the created cluster list by clicking on the clusters options.
+
+
+
+10. It will show you the list of all the created clusters.
+
+
+
+## 3. Prepare VM for connecting to Kubernetes cluster and deploy Pulsar Helm
chart on Kubernetes cluster.
+
+**Prerequisites**
+1. Install [IBM Cloud
CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli) and connect
to Kubernetes master node.
+
+2. Install [IBM Cloud CLI
Plugins](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_install)
to connect to IKS (IBM Kubernetes services). This is a required step.
+
+3. Install
[kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/) 1.23
or later versions.
+4. Install [Helm](https://helm.sh/docs/intro/install/).
+
+:::note
+
+Please install all the above things before running the below commands
+
+:::
+
+1. First take SSH of your VM with your private key. Run all the below commands
one by one.
+```bash
+ $ ibmcloud login
+ $ ibmcloud plugin list
+```
+
+Output
+
+
+2. For connection to the Kubernetes cluster, you will get a command in the
Kubernetes cluster section (Kubernetes console) as below.
+
+
+```bash
+ $ibmcloud ks cluster config --cluster ccql163t064kpvg5gg10
+```
+
+:::note
+
+This step is showing during creation of Kubernetes Cluster.
+
+:::
+
+
+
+3. After running the second and third commands shown in the above images, you
will get an output as below. You do not need to run the first command because
you've already logged in to IBM Cloud.
+
+Output
+
+
+> Now we are able to run commands of kubectl.
+
+## 4. Verify the deployment
+Make sure all the pods of Pulsar are running. Get the service URL and broker
URL for publishing and consuming the messages.
+
+
+
+> [Installation of Pulsar helm in minikube
cluster](https://pulsar.apache.org/docs/getting-started-helm/) this document
is for minikube cluster we are taking reference from that.
+
+1. Add Pulsar chart repo
+
+```bash
+$ helm repo add apache https://pulsar.apache.org/charts
+$ helm repo update
+$ helm repo list
+```
+
+Output
+
+
+2. Clone the Pulsar Helm chart repository, go inside the pulsar-helm-chart
directory
+
+```bash
+git clone https://github.com/apache/pulsar-helm-chart
+cd pulsar-helm-chart
+```
+
+3. Run the script`prepare_helm_release.sh`to create secrets required for
installing the Apache Pulsar Helm chart. The username `pulsar` and password
`pulsar` are used for logging into the Grafana dashboard and Pulsar Manager.
+
+:::note
+
+When running the script, you can use `-n` to specify the Kubernetes namespace
where the Pulsar Helm chart is installed,`-k`to define the Pulsar Helm release
name, and `-c` to create the Kubernetes namespace. For more information about
the script, run `./scripts/pulsar/prepare_helm_release.sh --help`.
+
+:::
+
+```bash
+ ./scripts/pulsar/prepare_helm_release.sh -n default -k asia -c
+```
+
+Output
+
+
+4. Use the Pulsar Helm chart to install a Pulsar cluster to Kubernetes.
+
+```bash
+helm install --values examples/values-minikube.yaml --set initialize=true asia
apache/pulsar
+```
+
+:::note
+
+You need to specify `--set initialize=true` when installing Pulsar the first
time. This command installs and starts Apache Pulsar.
+
+:::
+
+Output
+
+
+5. Check the status of all pods.
+
+```bash
+kubectl get pods
+```
+If all pods start up successfully, you can see that `STATUS` is changed to
`Running` or `Completed`.
+
+Output
+
+
+
+6. Check the status of all services.
+
+```bash
+ kubectl get services
+```
+
+Output
+
+
+
+The output shows both `services URL` and `broker URL`.
+Proxy external IPs are the ports changed just now:
+- Service URL port is 80.
+- Broker URL port is 6650. This is default.
+If you execute all the commands successfully, you can use the Pulsar client to
connect to clusters and produce and consume messages through proxy external
IPs.
diff --git a/versioned_docs/version-2.9.x/deploy-ibm.md
b/versioned_docs/version-2.9.x/deploy-ibm.md
index 51e01c24069..1ac850d8811 100644
--- a/versioned_docs/version-2.9.x/deploy-ibm.md
+++ b/versioned_docs/version-2.9.x/deploy-ibm.md
@@ -14,9 +14,9 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
4. [Verify the deployment.](#run-kubectl-commands-to-verify-the-deployment)
-#### Create VM on IBM Cloud
+## 1. Create VM on IBM Cloud
-1. Go to [IBM Cloud]( https://cloud.ibm.com/login) and login with your
credentials.
+1. Go to [IBM Cloud](
https://cloud.ibm.com/?cm_sp=freelancer-_-pulsar-iks-_-cta) and login with
your credentials.
2. Search for Virtual Server.
3. Select Virtual Server for Classic.
@@ -61,11 +61,11 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-13. Check the devices list, click on the menu option on the same page.
+13. Check the devices list, and click on the menu option on the same page.
-#### Create Kubernetes Cluster on IBM
+## 2. Create Kubernetes Cluster on IBM
1. Search for the Kubernetes services
@@ -75,7 +75,7 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-3. Select the infrastructure type we are going with the classic and also
select the Kubernetes version .
+3. Select the infrastructure type we are going with the classic and also
select the Kubernetes version.
@@ -102,7 +102,7 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-9. Check the created cluster list through clicking on the clusters options
+9. Check the created cluster list by clicking on the clusters options
@@ -110,7 +110,7 @@ Deploying a Pulsar cluster on IBM cloud consists of the
following steps:
-## Step 3: Prepare VM for connecting to Kubernetes cluster and deploy Pulsar
Helm chart on Kubernetes cluster.
+## 3. Prepare VM for connecting to Kubernetes cluster and deploy Pulsar Helm
chart on Kubernetes cluster.
**Prerequisites**
1. Install [IBM Cloud
CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli) and connect
to Kubernetes master node.
@@ -157,7 +157,7 @@ Output
> Now we are able to run commands of kubectl.
-## Verify the deployment
+## 4. Verify the deployment
Make sure all the pods of Pulsar are running. Get the service URL and broker
URL for publishing and consuming the messages.
@@ -182,11 +182,11 @@ git clone https://github.com/apache/pulsar-helm-chart
cd pulsar-helm-chart
```
-3. Run the script`prepare_helm_release.sh`to create secrets required for
installing the Apache Pulsar Helm chart. The username`pulsar`and
password`pulsar`are used for logging into the Grafana dashboard and Pulsar
Manager.
+3. Run the script `prepare_helm_release.sh` to create secrets required for
installing the Apache Pulsar Helm chart. The username `pulsar` and password
`pulsar` are used for logging into the Grafana dashboard and Pulsar Manager.
:::note
-When running the script, you can use`-n`to specify the Kubernetes namespace
where the Pulsar Helm chart is installed,`-k`to define the Pulsar Helm release
name, and`-c`to create the Kubernetes namespace. For more information about the
script, run `./scripts/pulsar/prepare_helm_release.sh --help`.
+When running the script, you can use `-n` to specify the Kubernetes namespace
where the Pulsar Helm chart is installed, `-k` to define the Pulsar Helm
release name, and `-c` to create the Kubernetes namespace. For more information
about the script, run `./scripts/pulsar/prepare_helm_release.sh --help`.
:::
@@ -205,7 +205,7 @@ helm install --values examples/values-minikube.yaml --set
initialize=true asia a
:::note
-You need to specify`--set initialize=true`when installing Pulsar the first
time. This command installs and starts Apache Pulsar.
+You need to specify `--set initialize=true` when installing Pulsar the first
time. This command installs and starts Apache Pulsar.
:::
@@ -217,7 +217,7 @@ Output
```bash
kubectl get pods
```
-If all pods start up successfully, you can see that `STATUS`is changed
to`Running`or`Completed`.
+If all pods start up successfully, you can see that `STATUS` is changed to
`Running` or `Completed`.
Output
@@ -237,4 +237,4 @@ The output shows both `services URL` and `broker URL`.
Proxy external IPs are the ports changed just now:
- Service URL port is 80.
- Broker URL port is 6650. This is default.
-If you execute all the commands successfully, you can use the Pulsar client to
connect to ?? clusters and produce and consume messages through proxy external
IPs.
+If you execute all the commands successfully, you can use the Pulsar client to
connect to clusters and produce and consume messages through proxy external
IPs.
