michaeljmarshall commented on a change in pull request #14551:
URL: https://github.com/apache/pulsar/pull/14551#discussion_r821018933



##########
File path: site2/docs/getting-started-standalone.md
##########
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
 > **Note**  
 > * If you are running Pulsar in a bare metal cluster, make sure `connectors` 
 > tarball is unzipped in every pulsar directory of the broker (or in every 
 > pulsar directory of function-worker if you are running a separate worker 
 > cluster for Pulsar Functions).
 > 
-> * If you are [running Pulsar in Docker](getting-started-docker.md) or 
deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes.md) or 
DC/OS, you can use the `apachepulsar/pulsar-all` image instead of the 
`apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already 
bundled [all builtin connectors](io-overview.md#working-with-connectors).
+> * If you are [running Pulsar in Docker](getting-started-docker.md) or 
deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes.md) or 
[DC/OS](https://dcos.io/), you can use the `apachepulsar/pulsar-all` image 
instead of the `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has 
already bundled [all builtin 
connectors](io-overview.md#working-with-connectors).

Review comment:
       I agree with that approach @Anonymitaet.




-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to