You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by ur...@apache.org on 2022/03/07 06:03:05 UTC
[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#71b936d)
This is an automated email from the ASF dual-hosted git repository.
urfree 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 270d331 Docs sync done from apache/pulsar(#71b936d)
270d331 is described below
commit 270d331f79cebd45f70ff593c45e76b8f51227f3
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Mon Mar 7 06:02:58 2022 +0000
Docs sync done from apache/pulsar(#71b936d)
---
site2/docs/getting-started-standalone.md | 2 +-
site2/website-next/docs/standalone.md | 2 +-
.../website-next/versioned_docs/version-2.2.0/functions-deploying.md | 2 +-
site2/website-next/versioned_docs/version-2.2.0/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.2.1/standalone.md | 4 ++--
.../website-next/versioned_docs/version-2.3.0/functions-deploying.md | 2 +-
site2/website-next/versioned_docs/version-2.3.0/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.3.1/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.3.2/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.4.0/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.4.1/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.4.1/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.4.2/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.4.2/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.5.0/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.5.1/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.5.2/standalone.md | 2 +-
site2/website-next/versioned_docs/version-2.6.0/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.6.0/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.1/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.6.1/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.2/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.6.2/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.3/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.6.3/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.6.4/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.6.4/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.0/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.7.0/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.1/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.7.1/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.2/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.7.2/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.3/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.7.3/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.7.4/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.7.4/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.0/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.8.0/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.1/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.8.1/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.8.2/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.8.2/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.9.0/deploy-dcos.md | 2 +-
site2/website-next/versioned_docs/version-2.9.0/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.9.0/standalone.md | 4 ++--
site2/website-next/versioned_docs/version-2.9.1/deploy-dcos.md | 2 +-
site2/website-next/versioned_docs/version-2.9.1/functions-deploy.md | 2 +-
site2/website-next/versioned_docs/version-2.9.1/standalone.md | 4 ++--
site2/website-next/versioned_sidebars/version-2.2.0-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.2.1-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.3.0-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.3.1-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.3.2-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.4.0-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.4.1-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.4.2-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.5.0-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.5.1-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.5.2-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.6.0-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.6.1-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.6.2-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.6.3-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.6.4-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.7.0-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.7.1-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.7.2-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.7.3-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.7.4-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.8.0-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.8.1-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.8.2-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.9.0-sidebars.json | 4 ----
site2/website-next/versioned_sidebars/version-2.9.1-sidebars.json | 4 ----
.../versioned_docs/version-2.1.0-incubating/functions-deploying.md | 2 +-
.../version-2.1.0-incubating/getting-started-standalone.md | 2 +-
.../versioned_docs/version-2.1.1-incubating/functions-deploying.md | 2 +-
.../version-2.1.1-incubating/getting-started-standalone.md | 2 +-
site2/website/versioned_docs/version-2.2.0/functions-deploying.md | 2 +-
.../versioned_docs/version-2.2.0/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.2.1/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.3.0/functions-deploying.md | 2 +-
.../versioned_docs/version-2.3.0/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.3.1/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.3.2/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.4.0/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.4.1/functions-deploy.md | 2 +-
.../versioned_docs/version-2.4.1/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.4.2/functions-deploy.md | 2 +-
.../versioned_docs/version-2.4.2/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.5.0/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.5.1/standalone.md | 4 ++--
site2/website/versioned_docs/version-2.6.0/functions-deploy.md | 2 +-
.../versioned_docs/version-2.6.0/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.6.1/functions-deploy.md | 2 +-
.../versioned_docs/version-2.6.1/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.6.2/functions-deploy.md | 2 +-
.../versioned_docs/version-2.6.2/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.6.3/functions-deploy.md | 2 +-
.../versioned_docs/version-2.6.3/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.6.4/functions-deploy.md | 2 +-
.../versioned_docs/version-2.6.4/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.7.0/functions-deploy.md | 2 +-
.../versioned_docs/version-2.7.0/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.7.1/functions-deploy.md | 2 +-
.../versioned_docs/version-2.7.1/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.7.2/functions-deploy.md | 2 +-
.../versioned_docs/version-2.7.2/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.7.3/functions-deploy.md | 2 +-
.../versioned_docs/version-2.7.3/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.7.4/functions-deploy.md | 2 +-
.../versioned_docs/version-2.7.4/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.8.0/functions-deploy.md | 2 +-
.../versioned_docs/version-2.8.0/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.8.1/functions-deploy.md | 2 +-
.../versioned_docs/version-2.8.1/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.8.2/functions-deploy.md | 2 +-
.../versioned_docs/version-2.8.2/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.9.0/deploy-dcos.md | 2 +-
site2/website/versioned_docs/version-2.9.0/functions-deploy.md | 2 +-
.../versioned_docs/version-2.9.0/getting-started-standalone.md | 4 ++--
site2/website/versioned_docs/version-2.9.1/deploy-dcos.md | 2 +-
site2/website/versioned_docs/version-2.9.1/functions-deploy.md | 2 +-
.../versioned_docs/version-2.9.1/getting-started-standalone.md | 4 ++--
.../website/versioned_sidebars/version-2.1.0-incubating-sidebars.json | 1 -
.../website/versioned_sidebars/version-2.1.1-incubating-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.2.0-sidebars.json | 3 +--
site2/website/versioned_sidebars/version-2.2.1-sidebars.json | 3 +--
site2/website/versioned_sidebars/version-2.3.0-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.3.1-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.3.2-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.4.0-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.4.1-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.4.2-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.5.0-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.5.1-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.5.2-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.6.0-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.6.1-sidebars.json | 3 +--
site2/website/versioned_sidebars/version-2.6.2-sidebars.json | 3 +--
site2/website/versioned_sidebars/version-2.6.3-sidebars.json | 3 +--
site2/website/versioned_sidebars/version-2.6.4-sidebars.json | 3 +--
site2/website/versioned_sidebars/version-2.7.0-sidebars.json | 3 +--
site2/website/versioned_sidebars/version-2.7.1-sidebars.json | 3 +--
site2/website/versioned_sidebars/version-2.7.2-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.7.3-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.7.4-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.8.0-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.8.1-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.8.2-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.9.0-sidebars.json | 1 -
site2/website/versioned_sidebars/version-2.9.1-sidebars.json | 1 -
153 files changed, 157 insertions(+), 289 deletions(-)
diff --git a/site2/docs/getting-started-standalone.md b/site2/docs/getting-started-standalone.md
index 94449f5..36c105c 100644
--- a/site2/docs/getting-started-standalone.md
+++ b/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).
### Install tiered storage offloaders (optional)
diff --git a/site2/website-next/docs/standalone.md b/site2/website-next/docs/standalone.md
index 738bccf..243a27f 100644
--- a/site2/website-next/docs/standalone.md
+++ b/site2/website-next/docs/standalone.md
@@ -122,7 +122,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) 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) 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).
:::
diff --git a/site2/website-next/versioned_docs/version-2.2.0/functions-deploying.md b/site2/website-next/versioned_docs/version-2.2.0/functions-deploying.md
index 8ad8dbe..fe10138 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/functions-deploying.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/functions-deploying.md
@@ -20,7 +20,7 @@ Cluster mode | The function runs *inside of* your Pulsar cluster, on the same ma
In order to deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more
If you're running a non-[standalone](reference-terminology.md#standalone) cluster, you'll need to obtain the service URL for the cluster. How you obtain the service URL will depend on how you deployed your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.2.0/standalone.md b/site2/website-next/versioned_docs/version-2.2.0/standalone.md
index c38e9b4..d80c0b6 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/standalone.md
@@ -113,7 +113,7 @@ pulsar-io-twitter-@pulsar:version@.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos)),
+> If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) or [DC/OS](https://dcos.io/)),
> you can use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
## Installing Tiered Storage Offloaders (optional)
@@ -162,7 +162,7 @@ For more details of how to configure tiered storage feature, you could reference
>
> If you are running Pulsar in a bare metal cluster, you need to make sure `offloaders` tarball is unzipped in every broker's pulsar directory
>
-> 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 [DCOS](deploy-dcos)),
+> If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) or [DC/OS](https://dcos.io/)),
> you can use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
diff --git a/site2/website-next/versioned_docs/version-2.2.1/standalone.md b/site2/website-next/versioned_docs/version-2.2.1/standalone.md
index f905bd6..7d70de4 100644
--- a/site2/website-next/versioned_docs/version-2.2.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.2.1/standalone.md
@@ -113,7 +113,7 @@ pulsar-io-twitter-@pulsar:version@.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos)),
+> If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) or [DC/OS](https://dcos.io/)),
> you can use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
## Installing Tiered Storage Offloaders (optional)
@@ -162,7 +162,7 @@ For more details of how to configure tiered storage feature, you could reference
>
> If you are running Pulsar in a bare metal cluster, you need to make sure `offloaders` tarball is unzipped in every broker's pulsar directory
>
-> 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 [DCOS](deploy-dcos)),
+> If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) or [DC/OS](https://dcos.io/)),
> you can use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
diff --git a/site2/website-next/versioned_docs/version-2.3.0/functions-deploying.md b/site2/website-next/versioned_docs/version-2.3.0/functions-deploying.md
index 8ad8dbe..fe10138 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/functions-deploying.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/functions-deploying.md
@@ -20,7 +20,7 @@ Cluster mode | The function runs *inside of* your Pulsar cluster, on the same ma
In order to deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more
If you're running a non-[standalone](reference-terminology.md#standalone) cluster, you'll need to obtain the service URL for the cluster. How you obtain the service URL will depend on how you deployed your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.3.0/standalone.md b/site2/website-next/versioned_docs/version-2.3.0/standalone.md
index d2ab5af..4c501cb 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/standalone.md
@@ -104,7 +104,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos)),
+> If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) or [DC/OS](https://dcos.io/)),
> you can use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
## Installing Tiered Storage Offloaders (optional)
@@ -153,7 +153,7 @@ For more details of how to configure tiered storage feature, you could reference
>
> If you are running Pulsar in a bare metal cluster, you need to make sure `offloaders` tarball is unzipped in every broker's pulsar directory
>
-> 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 [DCOS](deploy-dcos)),
+> If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) or [DC/OS](https://dcos.io/)),
> you can use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
diff --git a/site2/website-next/versioned_docs/version-2.3.1/standalone.md b/site2/website-next/versioned_docs/version-2.3.1/standalone.md
index 4412833..594d19a 100644
--- a/site2/website-next/versioned_docs/version-2.3.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.3.1/standalone.md
@@ -104,7 +104,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos)),
+> If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) or [DC/OS](https://dcos.io/)),
> you can use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
## Installing Tiered Storage Offloaders (optional)
@@ -153,7 +153,7 @@ For more details of how to configure tiered storage feature, you could reference
>
> If you are running Pulsar in a bare metal cluster, you need to make sure `offloaders` tarball is unzipped in every broker's pulsar directory
>
-> 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 [DCOS](deploy-dcos)),
+> If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) or [DC/OS](https://dcos.io/)),
> you can use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
diff --git a/site2/website-next/versioned_docs/version-2.3.2/standalone.md b/site2/website-next/versioned_docs/version-2.3.2/standalone.md
index 4c35336..932c1b0 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/standalone.md
@@ -112,7 +112,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -164,7 +164,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.4.0/standalone.md b/site2/website-next/versioned_docs/version-2.4.0/standalone.md
index deefb47..a9a8024 100644
--- a/site2/website-next/versioned_docs/version-2.4.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.4.0/standalone.md
@@ -112,7 +112,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -164,7 +164,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.4.1/functions-deploy.md b/site2/website-next/versioned_docs/version-2.4.1/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.4.1/standalone.md b/site2/website-next/versioned_docs/version-2.4.1/standalone.md
index 2403cb4..bbe0a2f 100644
--- a/site2/website-next/versioned_docs/version-2.4.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.4.1/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.4.2/functions-deploy.md b/site2/website-next/versioned_docs/version-2.4.2/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.4.2/standalone.md b/site2/website-next/versioned_docs/version-2.4.2/standalone.md
index 08d2ee5..c0eb637 100644
--- a/site2/website-next/versioned_docs/version-2.4.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.4.2/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.5.0/standalone.md b/site2/website-next/versioned_docs/version-2.5.0/standalone.md
index 2403cb4..bbe0a2f 100644
--- a/site2/website-next/versioned_docs/version-2.5.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.5.0/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.5.1/standalone.md b/site2/website-next/versioned_docs/version-2.5.1/standalone.md
index c2da381..a7d674f 100644
--- a/site2/website-next/versioned_docs/version-2.5.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.5.1/standalone.md
@@ -124,7 +124,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -176,7 +176,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.5.2/standalone.md b/site2/website-next/versioned_docs/version-2.5.2/standalone.md
index 738bccf..243a27f 100644
--- a/site2/website-next/versioned_docs/version-2.5.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.5.2/standalone.md
@@ -122,7 +122,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) 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) 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).
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.0/functions-deploy.md b/site2/website-next/versioned_docs/version-2.6.0/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.6.0/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.6.0/standalone.md b/site2/website-next/versioned_docs/version-2.6.0/standalone.md
index dd98935..4feeb2b 100644
--- a/site2/website-next/versioned_docs/version-2.6.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.0/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.1/functions-deploy.md b/site2/website-next/versioned_docs/version-2.6.1/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.6.1/standalone.md b/site2/website-next/versioned_docs/version-2.6.1/standalone.md
index dd98935..4feeb2b 100644
--- a/site2/website-next/versioned_docs/version-2.6.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.1/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.2/functions-deploy.md b/site2/website-next/versioned_docs/version-2.6.2/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.6.2/standalone.md b/site2/website-next/versioned_docs/version-2.6.2/standalone.md
index dd98935..4feeb2b 100644
--- a/site2/website-next/versioned_docs/version-2.6.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.2/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.3/functions-deploy.md b/site2/website-next/versioned_docs/version-2.6.3/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.6.3/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.6.3/standalone.md b/site2/website-next/versioned_docs/version-2.6.3/standalone.md
index dd98935..4feeb2b 100644
--- a/site2/website-next/versioned_docs/version-2.6.3/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.3/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.6.4/functions-deploy.md b/site2/website-next/versioned_docs/version-2.6.4/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.6.4/standalone.md b/site2/website-next/versioned_docs/version-2.6.4/standalone.md
index dd98935..4feeb2b 100644
--- a/site2/website-next/versioned_docs/version-2.6.4/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.6.4/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.0/functions-deploy.md b/site2/website-next/versioned_docs/version-2.7.0/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.7.0/standalone.md b/site2/website-next/versioned_docs/version-2.7.0/standalone.md
index dd98935..4feeb2b 100644
--- a/site2/website-next/versioned_docs/version-2.7.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.0/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.1/functions-deploy.md b/site2/website-next/versioned_docs/version-2.7.1/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.7.1/standalone.md b/site2/website-next/versioned_docs/version-2.7.1/standalone.md
index dd98935..4feeb2b 100644
--- a/site2/website-next/versioned_docs/version-2.7.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.1/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.2/functions-deploy.md b/site2/website-next/versioned_docs/version-2.7.2/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.7.2/standalone.md b/site2/website-next/versioned_docs/version-2.7.2/standalone.md
index c2da381..a7d674f 100644
--- a/site2/website-next/versioned_docs/version-2.7.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.2/standalone.md
@@ -124,7 +124,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -176,7 +176,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.3/functions-deploy.md b/site2/website-next/versioned_docs/version-2.7.3/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.7.3/standalone.md b/site2/website-next/versioned_docs/version-2.7.3/standalone.md
index b23223e..e1aa770 100644
--- a/site2/website-next/versioned_docs/version-2.7.3/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.3/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.7.4/functions-deploy.md b/site2/website-next/versioned_docs/version-2.7.4/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.7.4/standalone.md b/site2/website-next/versioned_docs/version-2.7.4/standalone.md
index b23223e..e1aa770 100644
--- a/site2/website-next/versioned_docs/version-2.7.4/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.7.4/standalone.md
@@ -118,7 +118,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -170,7 +170,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.0/functions-deploy.md b/site2/website-next/versioned_docs/version-2.8.0/functions-deploy.md
index 8ae4be9..51f1140 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.8.0/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.8.0/standalone.md b/site2/website-next/versioned_docs/version-2.8.0/standalone.md
index c2da381..a7d674f 100644
--- a/site2/website-next/versioned_docs/version-2.8.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.0/standalone.md
@@ -124,7 +124,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -176,7 +176,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.1/functions-deploy.md b/site2/website-next/versioned_docs/version-2.8.1/functions-deploy.md
index 5b761f0..10a8339 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.8.1/standalone.md b/site2/website-next/versioned_docs/version-2.8.1/standalone.md
index c2da381..a7d674f 100644
--- a/site2/website-next/versioned_docs/version-2.8.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.1/standalone.md
@@ -124,7 +124,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -176,7 +176,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.8.2/functions-deploy.md b/site2/website-next/versioned_docs/version-2.8.2/functions-deploy.md
index 5b761f0..10a8339 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.8.2/standalone.md b/site2/website-next/versioned_docs/version-2.8.2/standalone.md
index c2da381..a7d674f 100644
--- a/site2/website-next/versioned_docs/version-2.8.2/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.8.2/standalone.md
@@ -124,7 +124,7 @@ pulsar-io-aerospike-@pulsar:version@.nar
* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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).
:::
@@ -176,7 +176,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)),
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.0/deploy-dcos.md b/site2/website-next/versioned_docs/version-2.9.0/deploy-dcos.md
index 07f446e..49cf624 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/deploy-dcos.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/deploy-dcos.md
@@ -7,7 +7,7 @@ original_id: deploy-dcos
:::tip
-To enable all built-in [Pulsar IO](io-overview) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
+To enable all built-in [Pulsar IO](io-overview) connectors in your Pulsar deployment, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.0/functions-deploy.md b/site2/website-next/versioned_docs/version-2.9.0/functions-deploy.md
index 351e900..d8fe0fc 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.9.0/standalone.md b/site2/website-next/versioned_docs/version-2.9.0/standalone.md
index 0d5d8ba..004a31a 100644
--- a/site2/website-next/versioned_docs/version-2.9.0/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.0/standalone.md
@@ -123,7 +123,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 [DCOS](deploy-dcos)), 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) 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).
:::
@@ -174,7 +174,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)), you can use the `apachepulsar/pulsar-all` image instead of the `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.1/deploy-dcos.md b/site2/website-next/versioned_docs/version-2.9.1/deploy-dcos.md
index 07f446e..49cf624 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/deploy-dcos.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/deploy-dcos.md
@@ -7,7 +7,7 @@ original_id: deploy-dcos
:::tip
-To enable all built-in [Pulsar IO](io-overview) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
+To enable all built-in [Pulsar IO](io-overview) connectors in your Pulsar deployment, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
:::
diff --git a/site2/website-next/versioned_docs/version-2.9.1/functions-deploy.md b/site2/website-next/versioned_docs/version-2.9.1/functions-deploy.md
index 351e900..d8fe0fc 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/functions-deploy.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website-next/versioned_docs/version-2.9.1/standalone.md b/site2/website-next/versioned_docs/version-2.9.1/standalone.md
index 0d5d8ba..004a31a 100644
--- a/site2/website-next/versioned_docs/version-2.9.1/standalone.md
+++ b/site2/website-next/versioned_docs/version-2.9.1/standalone.md
@@ -123,7 +123,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 [DCOS](deploy-dcos)), 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) 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).
:::
@@ -174,7 +174,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
:::note
* If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
-* 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 [DCOS](deploy-dcos)), you can use the `apachepulsar/pulsar-all` image instead of the `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
+* If you are [running Pulsar in Docker](getting-started-docker.md) or deploying Pulsar using a docker image (e.g. [K8S](deploy-kubernetes) 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 tiered storage offloaders.
:::
diff --git a/site2/website-next/versioned_sidebars/version-2.2.0-sidebars.json b/site2/website-next/versioned_sidebars/version-2.2.0-sidebars.json
index 6f0d3a3..0d78822 100644
--- a/site2/website-next/versioned_sidebars/version-2.2.0-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.2.0-sidebars.json
@@ -172,10 +172,6 @@
},
{
"type": "doc",
- "id": "version-2.2.0/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.2.0/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.2.1-sidebars.json b/site2/website-next/versioned_sidebars/version-2.2.1-sidebars.json
index 96487d0..b7579e7 100644
--- a/site2/website-next/versioned_sidebars/version-2.2.1-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.2.1-sidebars.json
@@ -172,10 +172,6 @@
},
{
"type": "doc",
- "id": "version-2.2.1/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.2.1/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.3.0-sidebars.json b/site2/website-next/versioned_sidebars/version-2.3.0-sidebars.json
index be827d9..c456670 100644
--- a/site2/website-next/versioned_sidebars/version-2.3.0-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.3.0-sidebars.json
@@ -180,10 +180,6 @@
},
{
"type": "doc",
- "id": "version-2.3.0/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.3.0/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.3.1-sidebars.json b/site2/website-next/versioned_sidebars/version-2.3.1-sidebars.json
index 84d2a71..f7d8395 100644
--- a/site2/website-next/versioned_sidebars/version-2.3.1-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.3.1-sidebars.json
@@ -180,10 +180,6 @@
},
{
"type": "doc",
- "id": "version-2.3.1/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.3.1/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.3.2-sidebars.json b/site2/website-next/versioned_sidebars/version-2.3.2-sidebars.json
index 9a1f1f0..37c539c 100644
--- a/site2/website-next/versioned_sidebars/version-2.3.2-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.3.2-sidebars.json
@@ -184,10 +184,6 @@
},
{
"type": "doc",
- "id": "version-2.3.2/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.3.2/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.4.0-sidebars.json b/site2/website-next/versioned_sidebars/version-2.4.0-sidebars.json
index b5c604d..64e0723 100644
--- a/site2/website-next/versioned_sidebars/version-2.4.0-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.4.0-sidebars.json
@@ -192,10 +192,6 @@
},
{
"type": "doc",
- "id": "version-2.4.0/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.4.0/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.4.1-sidebars.json b/site2/website-next/versioned_sidebars/version-2.4.1-sidebars.json
index 495c102..fb2741e 100644
--- a/site2/website-next/versioned_sidebars/version-2.4.1-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.4.1-sidebars.json
@@ -210,10 +210,6 @@
},
{
"type": "doc",
- "id": "version-2.4.1/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.4.1/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.4.2-sidebars.json b/site2/website-next/versioned_sidebars/version-2.4.2-sidebars.json
index 1991c36..0f89806 100644
--- a/site2/website-next/versioned_sidebars/version-2.4.2-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.4.2-sidebars.json
@@ -210,10 +210,6 @@
},
{
"type": "doc",
- "id": "version-2.4.2/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.4.2/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.5.0-sidebars.json b/site2/website-next/versioned_sidebars/version-2.5.0-sidebars.json
index ccde2b4..0e47cec 100644
--- a/site2/website-next/versioned_sidebars/version-2.5.0-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.5.0-sidebars.json
@@ -244,10 +244,6 @@
},
{
"type": "doc",
- "id": "version-2.5.0/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.5.0/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.5.1-sidebars.json b/site2/website-next/versioned_sidebars/version-2.5.1-sidebars.json
index d1bceec..1d43df9 100644
--- a/site2/website-next/versioned_sidebars/version-2.5.1-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.5.1-sidebars.json
@@ -244,10 +244,6 @@
},
{
"type": "doc",
- "id": "version-2.5.1/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.5.1/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.5.2-sidebars.json b/site2/website-next/versioned_sidebars/version-2.5.2-sidebars.json
index 619220d..1abd66f 100644
--- a/site2/website-next/versioned_sidebars/version-2.5.2-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.5.2-sidebars.json
@@ -244,10 +244,6 @@
},
{
"type": "doc",
- "id": "version-2.5.2/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.5.2/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.6.0-sidebars.json b/site2/website-next/versioned_sidebars/version-2.6.0-sidebars.json
index 3944c0c..50724e3 100644
--- a/site2/website-next/versioned_sidebars/version-2.6.0-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.6.0-sidebars.json
@@ -248,10 +248,6 @@
},
{
"type": "doc",
- "id": "version-2.6.0/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.6.0/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.6.1-sidebars.json b/site2/website-next/versioned_sidebars/version-2.6.1-sidebars.json
index 982cc10..c98f86a 100644
--- a/site2/website-next/versioned_sidebars/version-2.6.1-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.6.1-sidebars.json
@@ -252,10 +252,6 @@
},
{
"type": "doc",
- "id": "version-2.6.1/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.6.1/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.6.2-sidebars.json b/site2/website-next/versioned_sidebars/version-2.6.2-sidebars.json
index a885096..e9acc0c 100644
--- a/site2/website-next/versioned_sidebars/version-2.6.2-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.6.2-sidebars.json
@@ -252,10 +252,6 @@
},
{
"type": "doc",
- "id": "version-2.6.2/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.6.2/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.6.3-sidebars.json b/site2/website-next/versioned_sidebars/version-2.6.3-sidebars.json
index a862207..f27d020 100644
--- a/site2/website-next/versioned_sidebars/version-2.6.3-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.6.3-sidebars.json
@@ -252,10 +252,6 @@
},
{
"type": "doc",
- "id": "version-2.6.3/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.6.3/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.6.4-sidebars.json b/site2/website-next/versioned_sidebars/version-2.6.4-sidebars.json
index 06ffacb..1ca67f0 100644
--- a/site2/website-next/versioned_sidebars/version-2.6.4-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.6.4-sidebars.json
@@ -248,10 +248,6 @@
},
{
"type": "doc",
- "id": "version-2.6.4/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.6.4/deploy-monitoring"
}
]
diff --git a/site2/website-next/versioned_sidebars/version-2.7.0-sidebars.json b/site2/website-next/versioned_sidebars/version-2.7.0-sidebars.json
index 0a90722..98c24ec 100644
--- a/site2/website-next/versioned_sidebars/version-2.7.0-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.7.0-sidebars.json
@@ -288,10 +288,6 @@
},
{
"type": "doc",
- "id": "version-2.7.0/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.7.0/deploy-docker"
},
{
diff --git a/site2/website-next/versioned_sidebars/version-2.7.1-sidebars.json b/site2/website-next/versioned_sidebars/version-2.7.1-sidebars.json
index 93c4639..771cd23 100644
--- a/site2/website-next/versioned_sidebars/version-2.7.1-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.7.1-sidebars.json
@@ -288,10 +288,6 @@
},
{
"type": "doc",
- "id": "version-2.7.1/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.7.1/deploy-docker"
},
{
diff --git a/site2/website-next/versioned_sidebars/version-2.7.2-sidebars.json b/site2/website-next/versioned_sidebars/version-2.7.2-sidebars.json
index b24e701..68ad23d 100644
--- a/site2/website-next/versioned_sidebars/version-2.7.2-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.7.2-sidebars.json
@@ -288,10 +288,6 @@
},
{
"type": "doc",
- "id": "version-2.7.2/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.7.2/deploy-docker"
},
{
diff --git a/site2/website-next/versioned_sidebars/version-2.7.3-sidebars.json b/site2/website-next/versioned_sidebars/version-2.7.3-sidebars.json
index 7bc352c..793492b 100644
--- a/site2/website-next/versioned_sidebars/version-2.7.3-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.7.3-sidebars.json
@@ -288,10 +288,6 @@
},
{
"type": "doc",
- "id": "version-2.7.3/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.7.3/deploy-docker"
},
{
diff --git a/site2/website-next/versioned_sidebars/version-2.7.4-sidebars.json b/site2/website-next/versioned_sidebars/version-2.7.4-sidebars.json
index 326c19b..df87371 100644
--- a/site2/website-next/versioned_sidebars/version-2.7.4-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.7.4-sidebars.json
@@ -288,10 +288,6 @@
},
{
"type": "doc",
- "id": "version-2.7.4/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.7.4/deploy-docker"
},
{
diff --git a/site2/website-next/versioned_sidebars/version-2.8.0-sidebars.json b/site2/website-next/versioned_sidebars/version-2.8.0-sidebars.json
index 4a16f86..cdc08e2 100644
--- a/site2/website-next/versioned_sidebars/version-2.8.0-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.8.0-sidebars.json
@@ -300,10 +300,6 @@
},
{
"type": "doc",
- "id": "version-2.8.0/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.8.0/deploy-docker"
},
{
diff --git a/site2/website-next/versioned_sidebars/version-2.8.1-sidebars.json b/site2/website-next/versioned_sidebars/version-2.8.1-sidebars.json
index f5da8bb..7fd9cca 100644
--- a/site2/website-next/versioned_sidebars/version-2.8.1-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.8.1-sidebars.json
@@ -300,10 +300,6 @@
},
{
"type": "doc",
- "id": "version-2.8.1/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.8.1/deploy-docker"
},
{
diff --git a/site2/website-next/versioned_sidebars/version-2.8.2-sidebars.json b/site2/website-next/versioned_sidebars/version-2.8.2-sidebars.json
index 10e818a..fb549b6 100644
--- a/site2/website-next/versioned_sidebars/version-2.8.2-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.8.2-sidebars.json
@@ -300,10 +300,6 @@
},
{
"type": "doc",
- "id": "version-2.8.2/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.8.2/deploy-docker"
},
{
diff --git a/site2/website-next/versioned_sidebars/version-2.9.0-sidebars.json b/site2/website-next/versioned_sidebars/version-2.9.0-sidebars.json
index 4b730c5..57a889a 100644
--- a/site2/website-next/versioned_sidebars/version-2.9.0-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.9.0-sidebars.json
@@ -300,10 +300,6 @@
},
{
"type": "doc",
- "id": "version-2.9.0/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.9.0/deploy-docker"
},
{
diff --git a/site2/website-next/versioned_sidebars/version-2.9.1-sidebars.json b/site2/website-next/versioned_sidebars/version-2.9.1-sidebars.json
index abb0767..adc7456 100644
--- a/site2/website-next/versioned_sidebars/version-2.9.1-sidebars.json
+++ b/site2/website-next/versioned_sidebars/version-2.9.1-sidebars.json
@@ -300,10 +300,6 @@
},
{
"type": "doc",
- "id": "version-2.9.1/deploy-dcos"
- },
- {
- "type": "doc",
"id": "version-2.9.1/deploy-docker"
},
{
diff --git a/site2/website/versioned_docs/version-2.1.0-incubating/functions-deploying.md b/site2/website/versioned_docs/version-2.1.0-incubating/functions-deploying.md
index a7370b9..41df2b1 100644
--- a/site2/website/versioned_docs/version-2.1.0-incubating/functions-deploying.md
+++ b/site2/website/versioned_docs/version-2.1.0-incubating/functions-deploying.md
@@ -20,7 +20,7 @@ Cluster mode | The function runs *inside of* your Pulsar cluster, on the same ma
In order to deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more
If you're running a non-[standalone](reference-terminology.md#standalone) cluster, you'll need to obtain the service URL for the cluster. How you obtain the service URL will depend on how you deployed your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.1.0-incubating/getting-started-standalone.md b/site2/website/versioned_docs/version-2.1.0-incubating/getting-started-standalone.md
index 0dc3221..a3822d9 100644
--- a/site2/website/versioned_docs/version-2.1.0-incubating/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.1.0-incubating/getting-started-standalone.md
@@ -105,7 +105,7 @@ pulsar-io-twitter-{{pulsar:version}}.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
### Starting the cluster
diff --git a/site2/website/versioned_docs/version-2.1.1-incubating/functions-deploying.md b/site2/website/versioned_docs/version-2.1.1-incubating/functions-deploying.md
index 6afb369..3fc2457 100644
--- a/site2/website/versioned_docs/version-2.1.1-incubating/functions-deploying.md
+++ b/site2/website/versioned_docs/version-2.1.1-incubating/functions-deploying.md
@@ -20,7 +20,7 @@ Cluster mode | The function runs *inside of* your Pulsar cluster, on the same ma
In order to deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more
If you're running a non-[standalone](reference-terminology.md#standalone) cluster, you'll need to obtain the service URL for the cluster. How you obtain the service URL will depend on how you deployed your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-standalone.md b/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-standalone.md
index f079319..91bf0e3 100644
--- a/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-standalone.md
@@ -104,7 +104,7 @@ pulsar-io-twitter-{{pulsar:version}}.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
### Starting the cluster
diff --git a/site2/website/versioned_docs/version-2.2.0/functions-deploying.md b/site2/website/versioned_docs/version-2.2.0/functions-deploying.md
index 0c9e064..0f1e64f 100644
--- a/site2/website/versioned_docs/version-2.2.0/functions-deploying.md
+++ b/site2/website/versioned_docs/version-2.2.0/functions-deploying.md
@@ -20,7 +20,7 @@ Cluster mode | The function runs *inside of* your Pulsar cluster, on the same ma
In order to deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more
If you're running a non-[standalone](reference-terminology.md#standalone) cluster, you'll need to obtain the service URL for the cluster. How you obtain the service URL will depend on how you deployed your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.2.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.2.0/getting-started-standalone.md
index 3dd2461..d9c2d38 100644
--- a/site2/website/versioned_docs/version-2.2.0/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.2.0/getting-started-standalone.md
@@ -104,7 +104,7 @@ pulsar-io-twitter-{{pulsar:version}}.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
## Installing Tiered Storage Offloaders (optional)
@@ -149,7 +149,7 @@ For more details of how to configure tiered storage feature, you could reference
>
> If you are running Pulsar in a bare metal cluster, you need to make sure `offloaders` tarball is unzipped in every broker's pulsar directory
>
-> 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
diff --git a/site2/website/versioned_docs/version-2.2.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.2.1/getting-started-standalone.md
index 4c75cc5..e3fe5a8 100644
--- a/site2/website/versioned_docs/version-2.2.1/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.2.1/getting-started-standalone.md
@@ -104,7 +104,7 @@ pulsar-io-twitter-{{pulsar:version}}.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
## Installing Tiered Storage Offloaders (optional)
@@ -149,7 +149,7 @@ For more details of how to configure tiered storage feature, you could reference
>
> If you are running Pulsar in a bare metal cluster, you need to make sure `offloaders` tarball is unzipped in every broker's pulsar directory
>
-> 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
diff --git a/site2/website/versioned_docs/version-2.3.0/functions-deploying.md b/site2/website/versioned_docs/version-2.3.0/functions-deploying.md
index f89bc1c..0078e34 100644
--- a/site2/website/versioned_docs/version-2.3.0/functions-deploying.md
+++ b/site2/website/versioned_docs/version-2.3.0/functions-deploying.md
@@ -20,7 +20,7 @@ Cluster mode | The function runs *inside of* your Pulsar cluster, on the same ma
In order to deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more
If you're running a non-[standalone](reference-terminology.md#standalone) cluster, you'll need to obtain the service URL for the cluster. How you obtain the service URL will depend on how you deployed your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.3.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.3.0/getting-started-standalone.md
index 3d0df1d..86c2a3a 100644
--- a/site2/website/versioned_docs/version-2.3.0/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.3.0/getting-started-standalone.md
@@ -95,7 +95,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
## Installing Tiered Storage Offloaders (optional)
@@ -140,7 +140,7 @@ For more details of how to configure tiered storage feature, you could reference
>
> If you are running Pulsar in a bare metal cluster, you need to make sure `offloaders` tarball is unzipped in every broker's pulsar directory
>
-> 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
diff --git a/site2/website/versioned_docs/version-2.3.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.3.1/getting-started-standalone.md
index 1fc6fe6..7bdeeb8 100644
--- a/site2/website/versioned_docs/version-2.3.1/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.3.1/getting-started-standalone.md
@@ -95,7 +95,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> If you are running Pulsar in a bare metal cluster, you need to make sure `connectors` tarball is unzipped in every broker's pulsar directory
> (or in every function-worker's pulsar directory 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled [all builtin connectors](io-overview.md#working-with-connectors).
## Installing Tiered Storage Offloaders (optional)
@@ -140,7 +140,7 @@ For more details of how to configure tiered storage feature, you could reference
>
> If you are running Pulsar in a bare metal cluster, you need to make sure `offloaders` tarball is unzipped in every broker's pulsar directory
>
-> 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 [DCOS](deploy-dcos.md)),
+> 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 `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
diff --git a/site2/website/versioned_docs/version-2.3.2/getting-started-standalone.md b/site2/website/versioned_docs/version-2.3.2/getting-started-standalone.md
index fb101c5..1404a2e 100644
--- a/site2/website/versioned_docs/version-2.3.2/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.3.2/getting-started-standalone.md
@@ -103,7 +103,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
##### Install tiered storage offloaders (optional)
@@ -148,7 +148,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.4.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.4.0/getting-started-standalone.md
index cbb2181..485d3be 100644
--- a/site2/website/versioned_docs/version-2.4.0/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.4.0/getting-started-standalone.md
@@ -103,7 +103,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -148,7 +148,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.4.1/functions-deploy.md b/site2/website/versioned_docs/version-2.4.1/functions-deploy.md
index c987106..ebf7f7a 100644
--- a/site2/website/versioned_docs/version-2.4.1/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.4.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.4.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.4.1/getting-started-standalone.md
index 31b9ea9..a80f443 100644
--- a/site2/website/versioned_docs/version-2.4.1/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.4.1/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.4.2/functions-deploy.md b/site2/website/versioned_docs/version-2.4.2/functions-deploy.md
index 6bee728..df409f9 100644
--- a/site2/website/versioned_docs/version-2.4.2/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.4.2/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.4.2/getting-started-standalone.md b/site2/website/versioned_docs/version-2.4.2/getting-started-standalone.md
index 56be876..2e4e50a 100644
--- a/site2/website/versioned_docs/version-2.4.2/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.4.2/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.5.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.5.0/getting-started-standalone.md
index f62516a..f39a5ff 100644
--- a/site2/website/versioned_docs/version-2.5.0/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.5.0/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.5.1/standalone.md b/site2/website/versioned_docs/version-2.5.1/standalone.md
index 0758fb9..cff185c 100644
--- a/site2/website/versioned_docs/version-2.5.1/standalone.md
+++ b/site2/website/versioned_docs/version-2.5.1/standalone.md
@@ -110,7 +110,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -155,7 +155,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.6.0/functions-deploy.md b/site2/website/versioned_docs/version-2.6.0/functions-deploy.md
index be4a5e8..3e22e71 100644
--- a/site2/website/versioned_docs/version-2.6.0/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.6.0/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.6.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.6.0/getting-started-standalone.md
index a36fa37..76abd7d 100644
--- a/site2/website/versioned_docs/version-2.6.0/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.6.0/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.6.1/functions-deploy.md b/site2/website/versioned_docs/version-2.6.1/functions-deploy.md
index 542bde6..52b4c5f 100644
--- a/site2/website/versioned_docs/version-2.6.1/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.6.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.6.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.6.1/getting-started-standalone.md
index f995956..33466d9 100644
--- a/site2/website/versioned_docs/version-2.6.1/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.6.1/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.6.2/functions-deploy.md b/site2/website/versioned_docs/version-2.6.2/functions-deploy.md
index ec33316..7fa0030 100644
--- a/site2/website/versioned_docs/version-2.6.2/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.6.2/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.6.2/getting-started-standalone.md b/site2/website/versioned_docs/version-2.6.2/getting-started-standalone.md
index feb70c8..66bf840 100644
--- a/site2/website/versioned_docs/version-2.6.2/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.6.2/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.6.3/functions-deploy.md b/site2/website/versioned_docs/version-2.6.3/functions-deploy.md
index 88a661c..16ee14d 100644
--- a/site2/website/versioned_docs/version-2.6.3/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.6.3/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.6.3/getting-started-standalone.md b/site2/website/versioned_docs/version-2.6.3/getting-started-standalone.md
index 3bb6d6b..6218ce8 100644
--- a/site2/website/versioned_docs/version-2.6.3/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.6.3/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.6.4/functions-deploy.md b/site2/website/versioned_docs/version-2.6.4/functions-deploy.md
index 5035ef9..692f6c2 100644
--- a/site2/website/versioned_docs/version-2.6.4/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.6.4/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.6.4/getting-started-standalone.md b/site2/website/versioned_docs/version-2.6.4/getting-started-standalone.md
index 83aa716..4a0a43e 100644
--- a/site2/website/versioned_docs/version-2.6.4/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.6.4/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.7.0/functions-deploy.md b/site2/website/versioned_docs/version-2.7.0/functions-deploy.md
index 5d85385..54df4d2 100644
--- a/site2/website/versioned_docs/version-2.7.0/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.7.0/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.7.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.7.0/getting-started-standalone.md
index f118c87..69d523b 100644
--- a/site2/website/versioned_docs/version-2.7.0/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.7.0/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.7.1/functions-deploy.md b/site2/website/versioned_docs/version-2.7.1/functions-deploy.md
index 3ab0125..309b117 100644
--- a/site2/website/versioned_docs/version-2.7.1/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.7.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.7.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.7.1/getting-started-standalone.md
index 7d3e853..d2c33d4 100644
--- a/site2/website/versioned_docs/version-2.7.1/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.7.1/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.7.2/functions-deploy.md b/site2/website/versioned_docs/version-2.7.2/functions-deploy.md
index f183b69..45528df 100644
--- a/site2/website/versioned_docs/version-2.7.2/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.7.2/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.7.2/getting-started-standalone.md b/site2/website/versioned_docs/version-2.7.2/getting-started-standalone.md
index 4b8f69f..2019939 100644
--- a/site2/website/versioned_docs/version-2.7.2/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.7.2/getting-started-standalone.md
@@ -110,7 +110,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -155,7 +155,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.7.3/functions-deploy.md b/site2/website/versioned_docs/version-2.7.3/functions-deploy.md
index a11aa4f..a5366ef 100644
--- a/site2/website/versioned_docs/version-2.7.3/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.7.3/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.7.3/getting-started-standalone.md b/site2/website/versioned_docs/version-2.7.3/getting-started-standalone.md
index e6fe6b9..d5f789f 100644
--- a/site2/website/versioned_docs/version-2.7.3/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.7.3/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.7.4/functions-deploy.md b/site2/website/versioned_docs/version-2.7.4/functions-deploy.md
index ceabfc2..185cd0f 100644
--- a/site2/website/versioned_docs/version-2.7.4/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.7.4/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.7.4/getting-started-standalone.md b/site2/website/versioned_docs/version-2.7.4/getting-started-standalone.md
index d1da2c4..3b1193f 100644
--- a/site2/website/versioned_docs/version-2.7.4/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.7.4/getting-started-standalone.md
@@ -106,7 +106,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -151,7 +151,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.8.0/functions-deploy.md b/site2/website/versioned_docs/version-2.8.0/functions-deploy.md
index 05e191b..1673fe3 100644
--- a/site2/website/versioned_docs/version-2.8.0/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.8.0/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.8.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.8.0/getting-started-standalone.md
index 5cc89b9..a1d6fca 100644
--- a/site2/website/versioned_docs/version-2.8.0/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.8.0/getting-started-standalone.md
@@ -110,7 +110,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -155,7 +155,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.8.1/functions-deploy.md b/site2/website/versioned_docs/version-2.8.1/functions-deploy.md
index 76eda08..b632b10 100644
--- a/site2/website/versioned_docs/version-2.8.1/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.8.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.8.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.8.1/getting-started-standalone.md
index b9c1994..30aae39 100644
--- a/site2/website/versioned_docs/version-2.8.1/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.8.1/getting-started-standalone.md
@@ -110,7 +110,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -155,7 +155,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.8.2/functions-deploy.md b/site2/website/versioned_docs/version-2.8.2/functions-deploy.md
index 1d54ded..0eba22d 100644
--- a/site2/website/versioned_docs/version-2.8.2/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.8.2/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.8.2/getting-started-standalone.md b/site2/website/versioned_docs/version-2.8.2/getting-started-standalone.md
index 9cb4a5e..5203e3c 100644
--- a/site2/website/versioned_docs/version-2.8.2/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.8.2/getting-started-standalone.md
@@ -110,7 +110,7 @@ pulsar-io-aerospike-{{pulsar:version}}.nar
> * 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 [DCOS](deploy-dcos.md)),
+> * 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).
### Install tiered storage offloaders (optional)
@@ -155,7 +155,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
>
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)),
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.9.0/deploy-dcos.md b/site2/website/versioned_docs/version-2.9.0/deploy-dcos.md
index 9b1b65a..17427de 100644
--- a/site2/website/versioned_docs/version-2.9.0/deploy-dcos.md
+++ b/site2/website/versioned_docs/version-2.9.0/deploy-dcos.md
@@ -6,7 +6,7 @@ original_id: deploy-dcos
---
> **Tips**
-> To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
+> To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
diff --git a/site2/website/versioned_docs/version-2.9.0/functions-deploy.md b/site2/website/versioned_docs/version-2.9.0/functions-deploy.md
index d0271af..51876ff 100644
--- a/site2/website/versioned_docs/version-2.9.0/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.9.0/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.9.0/getting-started-standalone.md b/site2/website/versioned_docs/version-2.9.0/getting-started-standalone.md
index 3b9ac81..1224b47 100644
--- a/site2/website/versioned_docs/version-2.9.0/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.9.0/getting-started-standalone.md
@@ -107,7 +107,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 [DCOS](deploy-dcos.md)), 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).
### Install tiered storage offloaders (optional)
@@ -149,7 +149,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
> **Note**
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)), you can use the `apachepulsar/pulsar-all` image instead of the `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_docs/version-2.9.1/deploy-dcos.md b/site2/website/versioned_docs/version-2.9.1/deploy-dcos.md
index f9f95a0..12930bc 100644
--- a/site2/website/versioned_docs/version-2.9.1/deploy-dcos.md
+++ b/site2/website/versioned_docs/version-2.9.1/deploy-dcos.md
@@ -6,7 +6,7 @@ original_id: deploy-dcos
---
> **Tips**
-> To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deploymente, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
+> To enable all built-in [Pulsar IO](io-overview.md) connectors in your Pulsar deployment, we recommend you use `apachepulsar/pulsar-all` image instead of `apachepulsar/pulsar` image; the former has already bundled [all built-in connectors](io-overview.md#working-with-connectors).
[DC/OS](https://dcos.io/) (the <strong>D</strong>ata<strong>C</strong>enter <strong>O</strong>perating <strong>S</strong>ystem) is a distributed operating system for deploying and managing applications and systems on [Apache Mesos](http://mesos.apache.org/). DC/OS is an open-source tool created and maintained by [Mesosphere](https://mesosphere.com/).
diff --git a/site2/website/versioned_docs/version-2.9.1/functions-deploy.md b/site2/website/versioned_docs/version-2.9.1/functions-deploy.md
index c672619..bd376fc 100644
--- a/site2/website/versioned_docs/version-2.9.1/functions-deploy.md
+++ b/site2/website/versioned_docs/version-2.9.1/functions-deploy.md
@@ -10,7 +10,7 @@ original_id: functions-deploy
To deploy and manage Pulsar Functions, you need to have a Pulsar cluster running. There are several options for this:
* You can run a [standalone cluster](getting-started-standalone.md) locally on your own machine.
-* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](deploy-dcos.md), and more.
+* You can deploy a Pulsar cluster on [Kubernetes](deploy-kubernetes.md), [Amazon Web Services](deploy-aws.md), [bare metal](deploy-bare-metal.md), [DC/OS](https://dcos.io/), and more.
If you run a non-[standalone](reference-terminology.md#standalone) cluster, you need to obtain the service URL for the cluster. How you obtain the service URL depends on how you deploy your Pulsar cluster.
diff --git a/site2/website/versioned_docs/version-2.9.1/getting-started-standalone.md b/site2/website/versioned_docs/version-2.9.1/getting-started-standalone.md
index 62e2369..778c508 100644
--- a/site2/website/versioned_docs/version-2.9.1/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.9.1/getting-started-standalone.md
@@ -107,7 +107,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 [DCOS](deploy-dcos.md)), 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).
### Install tiered storage offloaders (optional)
@@ -149,7 +149,7 @@ For more information on how to configure tiered storage, see [Tiered storage coo
> **Note**
> * If you are running Pulsar in a bare metal cluster, make sure that `offloaders` tarball is unzipped in every broker's pulsar directory.
>
-> * 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 [DCOS](deploy-dcos.md)), you can use the `apachepulsar/pulsar-all` image instead of the `apachepulsar/pulsar` image. `apachepulsar/pulsar-all` image has already bundled tiered storage offloaders.
+> * 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 tiered storage offloaders.
## Start Pulsar standalone
diff --git a/site2/website/versioned_sidebars/version-2.1.0-incubating-sidebars.json b/site2/website/versioned_sidebars/version-2.1.0-incubating-sidebars.json
index 8bcceae..162226c 100644
--- a/site2/website/versioned_sidebars/version-2.1.0-incubating-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.1.0-incubating-sidebars.json
@@ -39,7 +39,6 @@
"version-2.1.0-incubating-deploy-kubernetes",
"version-2.1.0-incubating-deploy-bare-metal",
"version-2.1.0-incubating-deploy-bare-metal-multi-cluster",
- "version-2.1.0-incubating-deploy-dcos",
"version-2.1.0-incubating-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.1.1-incubating-sidebars.json b/site2/website/versioned_sidebars/version-2.1.1-incubating-sidebars.json
index 3ade133..de02a8d 100644
--- a/site2/website/versioned_sidebars/version-2.1.1-incubating-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.1.1-incubating-sidebars.json
@@ -39,7 +39,6 @@
"version-2.1.1-incubating-deploy-kubernetes",
"version-2.1.1-incubating-deploy-bare-metal",
"version-2.1.1-incubating-deploy-bare-metal-multi-cluster",
- "version-2.1.1-incubating-deploy-dcos",
"version-2.1.1-incubating-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.2.0-sidebars.json b/site2/website/versioned_sidebars/version-2.2.0-sidebars.json
index 034ce9b..f76f8f8 100644
--- a/site2/website/versioned_sidebars/version-2.2.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.2.0-sidebars.json
@@ -43,8 +43,7 @@
"version-2.2.0-deploy-aws",
"version-2.2.0-deploy-kubernetes",
"version-2.2.0-deploy-bare-metal",
- "version-2.2.0-deploy-bare-metal-multi-cluster",
- "version-2.2.0-deploy-dcos",
+ "version-2.2.0-deploy-bare-metal-multi-cluster",
"version-2.2.0-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.2.1-sidebars.json b/site2/website/versioned_sidebars/version-2.2.1-sidebars.json
index d7c4078..769e780 100644
--- a/site2/website/versioned_sidebars/version-2.2.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.2.1-sidebars.json
@@ -43,8 +43,7 @@
"version-2.2.1-deploy-aws",
"version-2.2.1-deploy-kubernetes",
"version-2.2.1-deploy-bare-metal",
- "version-2.2.1-deploy-bare-metal-multi-cluster",
- "version-2.2.1-deploy-dcos",
+ "version-2.2.1-deploy-bare-metal-multi-cluster",
"version-2.2.1-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.3.0-sidebars.json b/site2/website/versioned_sidebars/version-2.3.0-sidebars.json
index 7d7cc56..1fb50d1 100644
--- a/site2/website/versioned_sidebars/version-2.3.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.3.0-sidebars.json
@@ -46,7 +46,6 @@
"version-2.3.0-deploy-kubernetes",
"version-2.3.0-deploy-bare-metal",
"version-2.3.0-deploy-bare-metal-multi-cluster",
- "version-2.3.0-deploy-dcos",
"version-2.3.0-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.3.1-sidebars.json b/site2/website/versioned_sidebars/version-2.3.1-sidebars.json
index 292cd9b..318dd95 100644
--- a/site2/website/versioned_sidebars/version-2.3.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.3.1-sidebars.json
@@ -46,7 +46,6 @@
"version-2.3.1-deploy-kubernetes",
"version-2.3.1-deploy-bare-metal",
"version-2.3.1-deploy-bare-metal-multi-cluster",
- "version-2.3.1-deploy-dcos",
"version-2.3.1-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.3.2-sidebars.json b/site2/website/versioned_sidebars/version-2.3.2-sidebars.json
index d6b40c4..878c995 100644
--- a/site2/website/versioned_sidebars/version-2.3.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.3.2-sidebars.json
@@ -47,7 +47,6 @@
"version-2.3.2-deploy-kubernetes",
"version-2.3.2-deploy-bare-metal",
"version-2.3.2-deploy-bare-metal-multi-cluster",
- "version-2.3.2-deploy-dcos",
"version-2.3.2-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.4.0-sidebars.json b/site2/website/versioned_sidebars/version-2.4.0-sidebars.json
index f0c1b61..21a1aa7 100644
--- a/site2/website/versioned_sidebars/version-2.4.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.4.0-sidebars.json
@@ -49,7 +49,6 @@
"version-2.4.0-deploy-kubernetes",
"version-2.4.0-deploy-bare-metal",
"version-2.4.0-deploy-bare-metal-multi-cluster",
- "version-2.4.0-deploy-dcos",
"version-2.4.0-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.4.1-sidebars.json b/site2/website/versioned_sidebars/version-2.4.1-sidebars.json
index 1cf8670..c5f5c1d 100644
--- a/site2/website/versioned_sidebars/version-2.4.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.4.1-sidebars.json
@@ -58,7 +58,6 @@
"version-2.4.1-deploy-kubernetes",
"version-2.4.1-deploy-bare-metal",
"version-2.4.1-deploy-bare-metal-multi-cluster",
- "version-2.4.1-deploy-dcos",
"version-2.4.1-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.4.2-sidebars.json b/site2/website/versioned_sidebars/version-2.4.2-sidebars.json
index 0eb88de..e5d5d98 100644
--- a/site2/website/versioned_sidebars/version-2.4.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.4.2-sidebars.json
@@ -58,7 +58,6 @@
"version-2.4.2-deploy-kubernetes",
"version-2.4.2-deploy-bare-metal",
"version-2.4.2-deploy-bare-metal-multi-cluster",
- "version-2.4.2-deploy-dcos",
"version-2.4.2-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.5.0-sidebars.json b/site2/website/versioned_sidebars/version-2.5.0-sidebars.json
index 6d7fb37..04b233a 100644
--- a/site2/website/versioned_sidebars/version-2.5.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.5.0-sidebars.json
@@ -63,7 +63,6 @@
"version-2.5.0-deploy-kubernetes",
"version-2.5.0-deploy-bare-metal",
"version-2.5.0-deploy-bare-metal-multi-cluster",
- "version-2.5.0-deploy-dcos",
"version-2.5.0-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.5.1-sidebars.json b/site2/website/versioned_sidebars/version-2.5.1-sidebars.json
index 45b1709..e5ed683 100644
--- a/site2/website/versioned_sidebars/version-2.5.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.5.1-sidebars.json
@@ -63,7 +63,6 @@
"version-2.5.1-deploy-kubernetes",
"version-2.5.1-deploy-bare-metal",
"version-2.5.1-deploy-bare-metal-multi-cluster",
- "version-2.5.1-deploy-dcos",
"version-2.5.1-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.5.2-sidebars.json b/site2/website/versioned_sidebars/version-2.5.2-sidebars.json
index 0335119..f24cac4 100644
--- a/site2/website/versioned_sidebars/version-2.5.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.5.2-sidebars.json
@@ -63,7 +63,6 @@
"version-2.5.2-deploy-kubernetes",
"version-2.5.2-deploy-bare-metal",
"version-2.5.2-deploy-bare-metal-multi-cluster",
- "version-2.5.2-deploy-dcos",
"version-2.5.2-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.6.0-sidebars.json b/site2/website/versioned_sidebars/version-2.6.0-sidebars.json
index 5ac849a..1bd5ded 100644
--- a/site2/website/versioned_sidebars/version-2.6.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.0-sidebars.json
@@ -64,7 +64,6 @@
"version-2.6.0-deploy-kubernetes",
"version-2.6.0-deploy-bare-metal",
"version-2.6.0-deploy-bare-metal-multi-cluster",
- "version-2.6.0-deploy-dcos",
"version-2.6.0-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.6.1-sidebars.json b/site2/website/versioned_sidebars/version-2.6.1-sidebars.json
index 0e8dcb4..a77631c 100644
--- a/site2/website/versioned_sidebars/version-2.6.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.1-sidebars.json
@@ -64,8 +64,7 @@
"version-2.6.1-deploy-aws",
"version-2.6.1-deploy-kubernetes",
"version-2.6.1-deploy-bare-metal",
- "version-2.6.1-deploy-bare-metal-multi-cluster",
- "version-2.6.1-deploy-dcos",
+ "version-2.6.1-deploy-bare-metal-multi-cluster",
"version-2.6.1-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.6.2-sidebars.json b/site2/website/versioned_sidebars/version-2.6.2-sidebars.json
index f7499bc..fe6e9c5 100644
--- a/site2/website/versioned_sidebars/version-2.6.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.2-sidebars.json
@@ -64,8 +64,7 @@
"version-2.6.2-deploy-aws",
"version-2.6.2-deploy-kubernetes",
"version-2.6.2-deploy-bare-metal",
- "version-2.6.2-deploy-bare-metal-multi-cluster",
- "version-2.6.2-deploy-dcos",
+ "version-2.6.2-deploy-bare-metal-multi-cluster",
"version-2.6.2-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.6.3-sidebars.json b/site2/website/versioned_sidebars/version-2.6.3-sidebars.json
index 1899e6f..56e247c 100644
--- a/site2/website/versioned_sidebars/version-2.6.3-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.3-sidebars.json
@@ -64,8 +64,7 @@
"version-2.6.3-deploy-aws",
"version-2.6.3-deploy-kubernetes",
"version-2.6.3-deploy-bare-metal",
- "version-2.6.3-deploy-bare-metal-multi-cluster",
- "version-2.6.3-deploy-dcos",
+ "version-2.6.3-deploy-bare-metal-multi-cluster",
"version-2.6.3-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.6.4-sidebars.json b/site2/website/versioned_sidebars/version-2.6.4-sidebars.json
index 7191da3..69165cc 100644
--- a/site2/website/versioned_sidebars/version-2.6.4-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.4-sidebars.json
@@ -63,8 +63,7 @@
"version-2.6.4-deploy-aws",
"version-2.6.4-deploy-kubernetes",
"version-2.6.4-deploy-bare-metal",
- "version-2.6.4-deploy-bare-metal-multi-cluster",
- "version-2.6.4-deploy-dcos",
+ "version-2.6.4-deploy-bare-metal-multi-cluster",
"version-2.6.4-deploy-monitoring"
],
"Administration": [
diff --git a/site2/website/versioned_sidebars/version-2.7.0-sidebars.json b/site2/website/versioned_sidebars/version-2.7.0-sidebars.json
index 62587a5..4e259d5 100644
--- a/site2/website/versioned_sidebars/version-2.7.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.0-sidebars.json
@@ -74,8 +74,7 @@
"version-2.7.0-deploy-aws",
"version-2.7.0-deploy-kubernetes",
"version-2.7.0-deploy-bare-metal",
- "version-2.7.0-deploy-bare-metal-multi-cluster",
- "version-2.7.0-deploy-dcos",
+ "version-2.7.0-deploy-bare-metal-multi-cluster",
"version-2.7.0-deploy-docker",
"version-2.7.0-deploy-monitoring"
],
diff --git a/site2/website/versioned_sidebars/version-2.7.1-sidebars.json b/site2/website/versioned_sidebars/version-2.7.1-sidebars.json
index 84214f2..d7b5412 100644
--- a/site2/website/versioned_sidebars/version-2.7.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.1-sidebars.json
@@ -74,8 +74,7 @@
"version-2.7.1-deploy-aws",
"version-2.7.1-deploy-kubernetes",
"version-2.7.1-deploy-bare-metal",
- "version-2.7.1-deploy-bare-metal-multi-cluster",
- "version-2.7.1-deploy-dcos",
+ "version-2.7.1-deploy-bare-metal-multi-cluster",
"version-2.7.1-deploy-docker",
"version-2.7.1-deploy-monitoring"
],
diff --git a/site2/website/versioned_sidebars/version-2.7.2-sidebars.json b/site2/website/versioned_sidebars/version-2.7.2-sidebars.json
index 24e1b61..1f9ba00 100644
--- a/site2/website/versioned_sidebars/version-2.7.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.2-sidebars.json
@@ -75,7 +75,6 @@
"version-2.7.2-deploy-kubernetes",
"version-2.7.2-deploy-bare-metal",
"version-2.7.2-deploy-bare-metal-multi-cluster",
- "version-2.7.2-deploy-dcos",
"version-2.7.2-deploy-docker",
"version-2.7.2-deploy-monitoring"
],
diff --git a/site2/website/versioned_sidebars/version-2.7.3-sidebars.json b/site2/website/versioned_sidebars/version-2.7.3-sidebars.json
index 7f83039..4c50f0a 100644
--- a/site2/website/versioned_sidebars/version-2.7.3-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.3-sidebars.json
@@ -75,7 +75,6 @@
"version-2.7.3-deploy-kubernetes",
"version-2.7.3-deploy-bare-metal",
"version-2.7.3-deploy-bare-metal-multi-cluster",
- "version-2.7.3-deploy-dcos",
"version-2.7.3-deploy-docker",
"version-2.7.3-deploy-monitoring"
],
diff --git a/site2/website/versioned_sidebars/version-2.7.4-sidebars.json b/site2/website/versioned_sidebars/version-2.7.4-sidebars.json
index 332df18..90512a6 100644
--- a/site2/website/versioned_sidebars/version-2.7.4-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.4-sidebars.json
@@ -75,7 +75,6 @@
"version-2.7.4-deploy-kubernetes",
"version-2.7.4-deploy-bare-metal",
"version-2.7.4-deploy-bare-metal-multi-cluster",
- "version-2.7.4-deploy-dcos",
"version-2.7.4-deploy-docker",
"version-2.7.4-deploy-monitoring"
],
diff --git a/site2/website/versioned_sidebars/version-2.8.0-sidebars.json b/site2/website/versioned_sidebars/version-2.8.0-sidebars.json
index 54957d3..d0a08e7 100644
--- a/site2/website/versioned_sidebars/version-2.8.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.8.0-sidebars.json
@@ -78,7 +78,6 @@
"version-2.8.0-deploy-kubernetes",
"version-2.8.0-deploy-bare-metal",
"version-2.8.0-deploy-bare-metal-multi-cluster",
- "version-2.8.0-deploy-dcos",
"version-2.8.0-deploy-docker",
"version-2.8.0-deploy-monitoring"
],
diff --git a/site2/website/versioned_sidebars/version-2.8.1-sidebars.json b/site2/website/versioned_sidebars/version-2.8.1-sidebars.json
index 7a5ecd2..fb31e5c 100644
--- a/site2/website/versioned_sidebars/version-2.8.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.8.1-sidebars.json
@@ -78,7 +78,6 @@
"version-2.8.1-deploy-kubernetes",
"version-2.8.1-deploy-bare-metal",
"version-2.8.1-deploy-bare-metal-multi-cluster",
- "version-2.8.1-deploy-dcos",
"version-2.8.1-deploy-docker",
"version-2.8.1-deploy-monitoring"
],
diff --git a/site2/website/versioned_sidebars/version-2.8.2-sidebars.json b/site2/website/versioned_sidebars/version-2.8.2-sidebars.json
index 75f0c79..7fdca5f 100644
--- a/site2/website/versioned_sidebars/version-2.8.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.8.2-sidebars.json
@@ -78,7 +78,6 @@
"version-2.8.2-deploy-kubernetes",
"version-2.8.2-deploy-bare-metal",
"version-2.8.2-deploy-bare-metal-multi-cluster",
- "version-2.8.2-deploy-dcos",
"version-2.8.2-deploy-docker",
"version-2.8.2-deploy-monitoring"
],
diff --git a/site2/website/versioned_sidebars/version-2.9.0-sidebars.json b/site2/website/versioned_sidebars/version-2.9.0-sidebars.json
index 6177e58..7476438 100644
--- a/site2/website/versioned_sidebars/version-2.9.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.9.0-sidebars.json
@@ -78,7 +78,6 @@
"version-2.9.0-deploy-kubernetes",
"version-2.9.0-deploy-bare-metal",
"version-2.9.0-deploy-bare-metal-multi-cluster",
- "version-2.9.0-deploy-dcos",
"version-2.9.0-deploy-docker",
"version-2.9.0-deploy-monitoring"
],
diff --git a/site2/website/versioned_sidebars/version-2.9.1-sidebars.json b/site2/website/versioned_sidebars/version-2.9.1-sidebars.json
index 00722c7..aeee6a3 100644
--- a/site2/website/versioned_sidebars/version-2.9.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.9.1-sidebars.json
@@ -78,7 +78,6 @@
"version-2.9.1-deploy-kubernetes",
"version-2.9.1-deploy-bare-metal",
"version-2.9.1-deploy-bare-metal-multi-cluster",
- "version-2.9.1-deploy-dcos",
"version-2.9.1-deploy-docker",
"version-2.9.1-deploy-monitoring"
],