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 cc597786deb [doc][feat] Added doc to deploy a pulsar cluster on IBM
cloud services (#399)
cc597786deb is described below
commit cc597786deb70883025f39e71c71ab662c59d625
Author: Rakesh Soni <[email protected]>
AuthorDate: Wed Feb 22 08:08:00 2023 +0530
[doc][feat] Added doc to deploy a pulsar cluster on IBM cloud services
(#399)
---
static/assets/IBMCloud/Consumer_screen_result.png | Bin 0 -> 62328 bytes
static/assets/IBMCloud/HelmInstall.png | Bin 0 -> 41629 bytes
static/assets/IBMCloud/HelmOutPut.png | Bin 0 -> 65646 bytes
static/assets/IBMCloud/Helmrepo.png | Bin 0 -> 5523 bytes
static/assets/IBMCloud/IBMLogin.png | Bin 0 -> 34147 bytes
static/assets/IBMCloud/IKSConnect.png | Bin 0 -> 17842 bytes
static/assets/IBMCloud/Install Helm.png | Bin 0 -> 41629 bytes
static/assets/IBMCloud/PodStatus.png | Bin 0 -> 19026 bytes
.../assets/IBMCloud/Producer_screenshot_result.png | Bin 0 -> 64513 bytes
static/assets/IBMCloud/Secretsout.png | Bin 0 -> 65646 bytes
static/assets/IBMCloud/Services.png | Bin 0 -> 27080 bytes
static/assets/IBMCloud/VM1.png | Bin 0 -> 117138 bytes
static/assets/IBMCloud/VM10.png | Bin 0 -> 63332 bytes
static/assets/IBMCloud/VM11.png | Bin 0 -> 72448 bytes
static/assets/IBMCloud/VM12.png | Bin 0 -> 48945 bytes
static/assets/IBMCloud/VM2.png | Bin 0 -> 72402 bytes
static/assets/IBMCloud/VM3.png | Bin 0 -> 91966 bytes
static/assets/IBMCloud/VM4.png | Bin 0 -> 88042 bytes
static/assets/IBMCloud/VM5.png | Bin 0 -> 74852 bytes
static/assets/IBMCloud/VM6.png | Bin 0 -> 85445 bytes
static/assets/IBMCloud/VM7.png | Bin 0 -> 82976 bytes
static/assets/IBMCloud/VM8.png | Bin 0 -> 63158 bytes
static/assets/IBMCloud/VM9.png | Bin 0 -> 56389 bytes
static/assets/IBMCloud/k8s1.png | Bin 0 -> 122706 bytes
static/assets/IBMCloud/k8s10.png | Bin 0 -> 59240 bytes
static/assets/IBMCloud/k8s11.png | Bin 0 -> 80829 bytes
static/assets/IBMCloud/k8s12.png | Bin 0 -> 45247 bytes
static/assets/IBMCloud/k8s2.png | Bin 0 -> 79825 bytes
static/assets/IBMCloud/k8s3.png | Bin 0 -> 76699 bytes
static/assets/IBMCloud/k8s4.png | Bin 0 -> 52581 bytes
static/assets/IBMCloud/k8s5.png | Bin 0 -> 62278 bytes
static/assets/IBMCloud/k8s6.png | Bin 0 -> 70510 bytes
static/assets/IBMCloud/k8s7.png | Bin 0 -> 93860 bytes
static/assets/IBMCloud/k8s8.png | Bin 0 -> 71944 bytes
static/assets/IBMCloud/k8s9.png | Bin 0 -> 78571 bytes
static/assets/IBMCloud/pod_cmd.png | Bin 0 -> 19026 bytes
versioned_docs/version-2.10.x/deploy-ibm.md | 245 +++++++++++++++++++++
versioned_docs/version-2.11.x/deploy-ibm.md | 15 ++
versioned_docs/version-2.9.x/deploy-ibm.md | 240 ++++++++++++++++++++
versioned_sidebars/version-2.10.x-sidebars.json | 4 +
versioned_sidebars/version-2.11.x-sidebars.json | 3 +-
versioned_sidebars/version-2.9.x-sidebars.json | 4 +
42 files changed, 510 insertions(+), 1 deletion(-)
diff --git a/static/assets/IBMCloud/Consumer_screen_result.png
b/static/assets/IBMCloud/Consumer_screen_result.png
new file mode 100644
index 00000000000..65d13a74fef
Binary files /dev/null and b/static/assets/IBMCloud/Consumer_screen_result.png
differ
diff --git a/static/assets/IBMCloud/HelmInstall.png
b/static/assets/IBMCloud/HelmInstall.png
new file mode 100644
index 00000000000..f07206dd8c3
Binary files /dev/null and b/static/assets/IBMCloud/HelmInstall.png differ
diff --git a/static/assets/IBMCloud/HelmOutPut.png
b/static/assets/IBMCloud/HelmOutPut.png
new file mode 100644
index 00000000000..59f603374c0
Binary files /dev/null and b/static/assets/IBMCloud/HelmOutPut.png differ
diff --git a/static/assets/IBMCloud/Helmrepo.png
b/static/assets/IBMCloud/Helmrepo.png
new file mode 100644
index 00000000000..706f5a69dc8
Binary files /dev/null and b/static/assets/IBMCloud/Helmrepo.png differ
diff --git a/static/assets/IBMCloud/IBMLogin.png
b/static/assets/IBMCloud/IBMLogin.png
new file mode 100644
index 00000000000..ea7505ed483
Binary files /dev/null and b/static/assets/IBMCloud/IBMLogin.png differ
diff --git a/static/assets/IBMCloud/IKSConnect.png
b/static/assets/IBMCloud/IKSConnect.png
new file mode 100644
index 00000000000..ead1dd8ae71
Binary files /dev/null and b/static/assets/IBMCloud/IKSConnect.png differ
diff --git a/static/assets/IBMCloud/Install Helm.png
b/static/assets/IBMCloud/Install Helm.png
new file mode 100644
index 00000000000..f07206dd8c3
Binary files /dev/null and b/static/assets/IBMCloud/Install Helm.png differ
diff --git a/static/assets/IBMCloud/PodStatus.png
b/static/assets/IBMCloud/PodStatus.png
new file mode 100644
index 00000000000..7cc2ed159b1
Binary files /dev/null and b/static/assets/IBMCloud/PodStatus.png differ
diff --git a/static/assets/IBMCloud/Producer_screenshot_result.png
b/static/assets/IBMCloud/Producer_screenshot_result.png
new file mode 100644
index 00000000000..3f2e35393f8
Binary files /dev/null and
b/static/assets/IBMCloud/Producer_screenshot_result.png differ
diff --git a/static/assets/IBMCloud/Secretsout.png
b/static/assets/IBMCloud/Secretsout.png
new file mode 100644
index 00000000000..59f603374c0
Binary files /dev/null and b/static/assets/IBMCloud/Secretsout.png differ
diff --git a/static/assets/IBMCloud/Services.png
b/static/assets/IBMCloud/Services.png
new file mode 100644
index 00000000000..fd9cc63e08b
Binary files /dev/null and b/static/assets/IBMCloud/Services.png differ
diff --git a/static/assets/IBMCloud/VM1.png b/static/assets/IBMCloud/VM1.png
new file mode 100644
index 00000000000..9240e607af2
Binary files /dev/null and b/static/assets/IBMCloud/VM1.png differ
diff --git a/static/assets/IBMCloud/VM10.png b/static/assets/IBMCloud/VM10.png
new file mode 100644
index 00000000000..d8987ff6bfa
Binary files /dev/null and b/static/assets/IBMCloud/VM10.png differ
diff --git a/static/assets/IBMCloud/VM11.png b/static/assets/IBMCloud/VM11.png
new file mode 100644
index 00000000000..663acf3e86b
Binary files /dev/null and b/static/assets/IBMCloud/VM11.png differ
diff --git a/static/assets/IBMCloud/VM12.png b/static/assets/IBMCloud/VM12.png
new file mode 100644
index 00000000000..59859f685db
Binary files /dev/null and b/static/assets/IBMCloud/VM12.png differ
diff --git a/static/assets/IBMCloud/VM2.png b/static/assets/IBMCloud/VM2.png
new file mode 100644
index 00000000000..d1195d60248
Binary files /dev/null and b/static/assets/IBMCloud/VM2.png differ
diff --git a/static/assets/IBMCloud/VM3.png b/static/assets/IBMCloud/VM3.png
new file mode 100644
index 00000000000..76ca84bc79a
Binary files /dev/null and b/static/assets/IBMCloud/VM3.png differ
diff --git a/static/assets/IBMCloud/VM4.png b/static/assets/IBMCloud/VM4.png
new file mode 100644
index 00000000000..2d050a605dd
Binary files /dev/null and b/static/assets/IBMCloud/VM4.png differ
diff --git a/static/assets/IBMCloud/VM5.png b/static/assets/IBMCloud/VM5.png
new file mode 100644
index 00000000000..d22e0dda54c
Binary files /dev/null and b/static/assets/IBMCloud/VM5.png differ
diff --git a/static/assets/IBMCloud/VM6.png b/static/assets/IBMCloud/VM6.png
new file mode 100644
index 00000000000..7dda619e1da
Binary files /dev/null and b/static/assets/IBMCloud/VM6.png differ
diff --git a/static/assets/IBMCloud/VM7.png b/static/assets/IBMCloud/VM7.png
new file mode 100644
index 00000000000..3db00d5a930
Binary files /dev/null and b/static/assets/IBMCloud/VM7.png differ
diff --git a/static/assets/IBMCloud/VM8.png b/static/assets/IBMCloud/VM8.png
new file mode 100644
index 00000000000..db80fe48e2c
Binary files /dev/null and b/static/assets/IBMCloud/VM8.png differ
diff --git a/static/assets/IBMCloud/VM9.png b/static/assets/IBMCloud/VM9.png
new file mode 100644
index 00000000000..adcb638de89
Binary files /dev/null and b/static/assets/IBMCloud/VM9.png differ
diff --git a/static/assets/IBMCloud/k8s1.png b/static/assets/IBMCloud/k8s1.png
new file mode 100644
index 00000000000..5ca218ad689
Binary files /dev/null and b/static/assets/IBMCloud/k8s1.png differ
diff --git a/static/assets/IBMCloud/k8s10.png b/static/assets/IBMCloud/k8s10.png
new file mode 100644
index 00000000000..057ac8981c7
Binary files /dev/null and b/static/assets/IBMCloud/k8s10.png differ
diff --git a/static/assets/IBMCloud/k8s11.png b/static/assets/IBMCloud/k8s11.png
new file mode 100644
index 00000000000..a8be08d3c72
Binary files /dev/null and b/static/assets/IBMCloud/k8s11.png differ
diff --git a/static/assets/IBMCloud/k8s12.png b/static/assets/IBMCloud/k8s12.png
new file mode 100644
index 00000000000..6b2b82414f0
Binary files /dev/null and b/static/assets/IBMCloud/k8s12.png differ
diff --git a/static/assets/IBMCloud/k8s2.png b/static/assets/IBMCloud/k8s2.png
new file mode 100644
index 00000000000..fcf404e2ae4
Binary files /dev/null and b/static/assets/IBMCloud/k8s2.png differ
diff --git a/static/assets/IBMCloud/k8s3.png b/static/assets/IBMCloud/k8s3.png
new file mode 100644
index 00000000000..1ba0ade3ee4
Binary files /dev/null and b/static/assets/IBMCloud/k8s3.png differ
diff --git a/static/assets/IBMCloud/k8s4.png b/static/assets/IBMCloud/k8s4.png
new file mode 100644
index 00000000000..32b192abe6d
Binary files /dev/null and b/static/assets/IBMCloud/k8s4.png differ
diff --git a/static/assets/IBMCloud/k8s5.png b/static/assets/IBMCloud/k8s5.png
new file mode 100644
index 00000000000..38c0f194dda
Binary files /dev/null and b/static/assets/IBMCloud/k8s5.png differ
diff --git a/static/assets/IBMCloud/k8s6.png b/static/assets/IBMCloud/k8s6.png
new file mode 100644
index 00000000000..c9a14a93e54
Binary files /dev/null and b/static/assets/IBMCloud/k8s6.png differ
diff --git a/static/assets/IBMCloud/k8s7.png b/static/assets/IBMCloud/k8s7.png
new file mode 100644
index 00000000000..c031da5880c
Binary files /dev/null and b/static/assets/IBMCloud/k8s7.png differ
diff --git a/static/assets/IBMCloud/k8s8.png b/static/assets/IBMCloud/k8s8.png
new file mode 100644
index 00000000000..dd63299264b
Binary files /dev/null and b/static/assets/IBMCloud/k8s8.png differ
diff --git a/static/assets/IBMCloud/k8s9.png b/static/assets/IBMCloud/k8s9.png
new file mode 100644
index 00000000000..c3ecd1a5ee1
Binary files /dev/null and b/static/assets/IBMCloud/k8s9.png differ
diff --git a/static/assets/IBMCloud/pod_cmd.png
b/static/assets/IBMCloud/pod_cmd.png
new file mode 100644
index 00000000000..7cc2ed159b1
Binary files /dev/null and b/static/assets/IBMCloud/pod_cmd.png differ
diff --git a/versioned_docs/version-2.10.x/deploy-ibm.md
b/versioned_docs/version-2.10.x/deploy-ibm.md
new file mode 100644
index 00000000000..eee86130455
--- /dev/null
+++ b/versioned_docs/version-2.10.x/deploy-ibm.md
@@ -0,0 +1,245 @@
+---
+id: deploy-ibm
+title: Apache Pulsar Installation on IBM Kubernetes Cluster through Helm chart
+sidebar_label: "IBM Cloud Services"
+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](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)
+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)
+
+
+#### Create VM on IBM Cloud
+
+1. Go to [IBM Cloud]( https://cloud.ibm.com/login) 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, click on the menu option on the same page.
+
+
+
+#### 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 through clicking on the clusters options
+
+
+
+10. It will show you the list of all the created clusters.
+
+
+
+## Step 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.
+
+## 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.11.x/deploy-ibm.md
b/versioned_docs/version-2.11.x/deploy-ibm.md
new file mode 100644
index 00000000000..61a03f5f6fc
--- /dev/null
+++ b/versioned_docs/version-2.11.x/deploy-ibm.md
@@ -0,0 +1,15 @@
+---
+id: deploy-ibm
+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](https://pulsar.apache.org/docs/2.10.x/helm-upgrade/).
+
+:::
+
+[Deploying a Pulsar cluster on IBM cloud you need to Follow this
link](/docs/2.10.x/deploy-ibm/)
\ No newline at end of file
diff --git a/versioned_docs/version-2.9.x/deploy-ibm.md
b/versioned_docs/version-2.9.x/deploy-ibm.md
new file mode 100644
index 00000000000..b0a7140e034
--- /dev/null
+++ b/versioned_docs/version-2.9.x/deploy-ibm.md
@@ -0,0 +1,240 @@
+---
+id: deploy-ibm
+title: Apache Pulsar Installation on IBM Kubernetes Cluster through Helm chart
+sidebar_label: "IBM Cloud Services"
+original_id: deploy-ibm
+---
+
+
+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)
+
+
+#### Create VM on IBM Cloud
+
+1. Go to [IBM Cloud]( https://cloud.ibm.com/login) 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, click on the menu option on the same page.
+
+
+
+#### 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 through clicking on the clusters options
+
+
+
+10. It will show you the list of all the created clusters.
+
+
+
+## Step 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.
+
+## 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_sidebars/version-2.10.x-sidebars.json
b/versioned_sidebars/version-2.10.x-sidebars.json
index f1a39d0cb55..68681d06f3f 100644
--- a/versioned_sidebars/version-2.10.x-sidebars.json
+++ b/versioned_sidebars/version-2.10.x-sidebars.json
@@ -290,6 +290,10 @@
"type": "doc",
"id": "version-2.10.x/deploy-aws"
},
+ {
+ "type": "doc",
+ "id": "version-2.10.x/deploy-ibm"
+ },
{
"type": "doc",
"id": "version-2.10.x/deploy-kubernetes"
diff --git a/versioned_sidebars/version-2.11.x-sidebars.json
b/versioned_sidebars/version-2.11.x-sidebars.json
index 8abd37b56bc..3225dcb6747 100644
--- a/versioned_sidebars/version-2.11.x-sidebars.json
+++ b/versioned_sidebars/version-2.11.x-sidebars.json
@@ -216,7 +216,8 @@
},
"items": [
"deploy-aws",
- {
+ "deploy-ibm",
+ {
"type": "category",
"label": "Kubernetes",
"link": {
diff --git a/versioned_sidebars/version-2.9.x-sidebars.json
b/versioned_sidebars/version-2.9.x-sidebars.json
index 7d9fa265b05..5d8c59b1ec8 100644
--- a/versioned_sidebars/version-2.9.x-sidebars.json
+++ b/versioned_sidebars/version-2.9.x-sidebars.json
@@ -294,6 +294,10 @@
"type": "doc",
"id": "version-2.9.x/deploy-aws"
},
+ {
+ "type": "doc",
+ "id": "version-2.9.x/deploy-ibm"
+ },
{
"type": "doc",
"id": "version-2.9.x/deploy-kubernetes"
