Huanli-Meng commented on a change in pull request #7667: URL: https://github.com/apache/pulsar/pull/7667#discussion_r461376285
########## File path: site2/docs/getting-started-helm.md ########## @@ -200,7 +200,7 @@ We use [Minikube](https://kubernetes.io/docs/getting-started-guides/minikube/) i You can use the Pulsar client to create producers and consumers to produce and consume messages. -By default, the Pulsar Helm chart exposes the Pulsar cluster through a Kubernetes `LoadBalancer`. In Minikube, you can use the following command to get the IP address of the proxy service. +By default, the Pulsar Helm chart exposes the Pulsar cluster through a Kubernetes `LoadBalancer`. In Minikube, you can use the following command to view the proxy service. Review comment: ```suggestion By default, the Pulsar Helm chart exposes the Pulsar cluster through a Kubernetes `LoadBalancer`. In Minikube, you can use the following command to check the proxy service. ``` ########## File path: site2/docs/getting-started-helm.md ########## @@ -212,19 +212,36 @@ You will see a similar output as below. pulsar-mini-proxy LoadBalancer 10.97.240.109 <pending> 80:32305/TCP,6650:31816/TCP 28m ``` -This output tells what are the node ports that Pulsar cluster's binary port and HTTP port are exposed to. The port after `80:` is the HTTP port while the port after `6650:` is the binary port. +This output tells what are the node ports that Pulsar cluster's binary port and HTTP port are mapped to. The port after `80:` is the HTTP port while the port after `6650:` is the binary port. -Then you can find the IP address of your Minikube server by running the following command. +Then you can find the IP address and exposed ports of your Minikube server by running the following command. ```bash -minikube ip +minikube service pulsar-mini-proxy -n pulsar ``` -At this point, you can get the service URLs to connect to your Pulsar client. +Example output which shows the exposed ip and ports in the second table Review comment: ```suggestion **Output** ``` ########## File path: site2/docs/getting-started-helm.md ########## @@ -212,19 +212,36 @@ You will see a similar output as below. pulsar-mini-proxy LoadBalancer 10.97.240.109 <pending> 80:32305/TCP,6650:31816/TCP 28m ``` -This output tells what are the node ports that Pulsar cluster's binary port and HTTP port are exposed to. The port after `80:` is the HTTP port while the port after `6650:` is the binary port. +This output tells what are the node ports that Pulsar cluster's binary port and HTTP port are mapped to. The port after `80:` is the HTTP port while the port after `6650:` is the binary port. -Then you can find the IP address of your Minikube server by running the following command. +Then you can find the IP address and exposed ports of your Minikube server by running the following command. ```bash -minikube ip +minikube service pulsar-mini-proxy -n pulsar ``` -At this point, you can get the service URLs to connect to your Pulsar client. +Example output which shows the exposed ip and ports in the second table +```bash +|-----------|-------------------|-------------|-------------------------| +| NAMESPACE | NAME | TARGET PORT | URL | +|-----------|-------------------|-------------|-------------------------| +| pulsar | pulsar-mini-proxy | http/80 | http://172.17.0.4:32305 | +| | | pulsar/6650 | http://172.17.0.4:31816 | +|-----------|-------------------|-------------|-------------------------| +🏃 Starting tunnel for service pulsar-mini-proxy. +|-----------|-------------------|-------------|------------------------| +| NAMESPACE | NAME | TARGET PORT | URL | +|-----------|-------------------|-------------|------------------------| +| pulsar | pulsar-mini-proxy | | http://127.0.0.1:61853 | +| | | | http://127.0.0.1:61854 | +|-----------|-------------------|-------------|------------------------| +``` + +At this point, you can get the service URLs to connect to your Pulsar client. Urls for this example: Review comment: ```suggestion At this point, you can get the service URLs to connect to your Pulsar client. Here are URL examples: ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
