This is an automated email from the ASF dual-hosted git repository.
liuyu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/master by this push:
new 7086ac43725 [fix][doc] Fix 404 URL issues (#15309)
7086ac43725 is described below
commit 7086ac43725ff48209b91a0c459103337a31b323
Author: Anonymitaet <[email protected]>
AuthorDate: Tue Apr 26 09:34:57 2022 +0800
[fix][doc] Fix 404 URL issues (#15309)
---
site2/docs/concepts-architecture-overview.md | 2 +-
site2/docs/concepts-proxy-sni-routing.md | 2 +-
site2/docs/getting-started-standalone.md | 2 +-
.../version-2.1.0-incubating/getting-started-standalone.md | 4 ++--
.../version-2.1.1-incubating/getting-started-clients.md | 2 +-
.../version-2.1.1-incubating/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.10.0/concepts-architecture-overview.md | 2 +-
.../versioned_docs/version-2.10.0/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.10.0/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.2.0/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.2.1/getting-started-standalone.md | 4 ++--
.../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 ++--
.../versioned_docs/version-2.4.1/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.4.2/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.5.0/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.5.1/concepts-architecture-overview.md | 2 +-
.../version-2.5.1/{standalone.md => getting-started-standalone.md} | 4 ++--
.../versioned_docs/version-2.6.0/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.6.1/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.6.1/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.6.2/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.6.2/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.6.3/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.6.3/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.6.4/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.6.4/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.7.0/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.7.0/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.7.1/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.7.1/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.7.2/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.7.2/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.7.3/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.7.3/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.7.4/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.7.4/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.8.0/concepts-architecture-overview.md | 2 +-
.../versioned_docs/version-2.8.0/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.8.0/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.8.1/concepts-architecture-overview.md | 2 +-
.../versioned_docs/version-2.8.1/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.8.1/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.8.2/concepts-architecture-overview.md | 2 +-
.../versioned_docs/version-2.8.2/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.8.2/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.8.3/concepts-architecture-overview.md | 2 +-
.../versioned_docs/version-2.8.3/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.8.3/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.9.0/concepts-architecture-overview.md | 2 +-
.../versioned_docs/version-2.9.0/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.9.0/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.9.1/concepts-architecture-overview.md | 2 +-
.../versioned_docs/version-2.9.1/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.9.1/getting-started-standalone.md | 4 ++--
.../versioned_docs/version-2.9.2/concepts-architecture-overview.md | 2 +-
.../versioned_docs/version-2.9.2/concepts-proxy-sni-routing.md | 2 +-
.../versioned_docs/version-2.9.2/getting-started-standalone.md | 4 ++--
.../website/versioned_sidebars/version-2.1.0-incubating-sidebars.json | 2 +-
.../website/versioned_sidebars/version-2.1.1-incubating-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.10.0-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.2.0-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.2.1-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.3.0-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.3.1-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.3.2-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.4.0-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.4.1-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.4.2-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.5.0-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.5.1-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.5.2-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.6.0-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.6.1-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.6.2-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.6.3-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.6.4-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.7.0-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.7.1-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.7.2-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.7.3-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.7.4-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.8.0-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.8.1-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.8.2-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.8.3-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.9.0-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.9.1-sidebars.json | 2 +-
site2/website/versioned_sidebars/version-2.9.2-sidebars.json | 2 +-
91 files changed, 121 insertions(+), 121 deletions(-)
diff --git a/site2/docs/concepts-architecture-overview.md
b/site2/docs/concepts-architecture-overview.md
index 14f81b8c336..7a257632337 100644
--- a/site2/docs/concepts-architecture-overview.md
+++ b/site2/docs/concepts-architecture-overview.md
@@ -45,7 +45,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
> Pulsar also supports more metadata backend services, including
> [ETCD](https://etcd.io/) and [RocksDB](http://rocksdb.org/) (for standalone
> Pulsar only).
diff --git a/site2/docs/concepts-proxy-sni-routing.md
b/site2/docs/concepts-proxy-sni-routing.md
index eabcf513bd4..08a20ae1aea 100644
--- a/site2/docs/concepts-proxy-sni-routing.md
+++ b/site2/docs/concepts-proxy-sni-routing.md
@@ -43,7 +43,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
diff --git a/site2/docs/getting-started-standalone.md
b/site2/docs/getting-started-standalone.md
index 2d0e760f37d..b7be56c5f96 100644
--- a/site2/docs/getting-started-standalone.md
+++ b/site2/docs/getting-started-standalone.md
@@ -1,5 +1,5 @@
---
-id: standalone
+id: getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
---
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 a3822d9cc11..42252731e17 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
@@ -1,8 +1,8 @@
---
-id: version-2.1.0-incubating-standalone
+id: version-2.1.0-incubating-getting-started-standalone
title: Setting up a local standalone cluster
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For the purposes of local development and testing, you can run Pulsar in
standalone mode on your own machine. Standalone mode includes a Pulsar broker
as well as the necessary ZooKeeper and BookKeeper components running inside of
a single Java Virtual Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-clients.md
b/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-clients.md
index c5aa1742699..893b2e11aaa 100644
---
a/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-clients.md
+++
b/site2/website/versioned_docs/version-2.1.1-incubating/getting-started-clients.md
@@ -43,7 +43,7 @@ There are also
[Doxygen](http://www.stack.nl/~dimitri/doxygen/)-generated API do
## Feature Matrix
-This matrix listing all the features among different languages in Pulsar
master can be found
[here](https://github.com/apache/incubator-pulsar/wiki/Client-Features-Matrix).
+This matrix listing all the features among different languages in Pulsar
master can be found
[here](https://github.com/apache/pulsar/wiki/PIP-108:-Pulsar-Feature-Matrix-(Client-and-Function)).
## Thirdparty Clients
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 91bf0e37e08..f2075babf9f 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
@@ -1,8 +1,8 @@
---
-id: version-2.1.1-incubating-standalone
+id: version-2.1.1-incubating-getting-started-standalone
title: Setting up a local standalone cluster
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For the purposes of local development and testing, you can run Pulsar in
standalone mode on your own machine. Standalone mode includes a Pulsar broker
as well as the necessary ZooKeeper and BookKeeper components running inside of
a single Java Virtual Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.10.0/concepts-architecture-overview.md
b/site2/website/versioned_docs/version-2.10.0/concepts-architecture-overview.md
index 832c9a487f9..739beda25d3 100644
---
a/site2/website/versioned_docs/version-2.10.0/concepts-architecture-overview.md
+++
b/site2/website/versioned_docs/version-2.10.0/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
> Pulsar also supports more metadata backend services, including
> [ETCD](https://etcd.io/) and [RocksDB](http://rocksdb.org/) (for standalone
> Pulsar only).
diff --git
a/site2/website/versioned_docs/version-2.10.0/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.10.0/concepts-proxy-sni-routing.md
index 48aefedda56..b54e57aad10 100644
--- a/site2/website/versioned_docs/version-2.10.0/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.10.0/concepts-proxy-sni-routing.md
@@ -44,7 +44,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
diff --git
a/site2/website/versioned_docs/version-2.10.0/getting-started-standalone.md
b/site2/website/versioned_docs/version-2.10.0/getting-started-standalone.md
index 72a70e2487f..925a64b1a93 100644
--- a/site2/website/versioned_docs/version-2.10.0/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.10.0/getting-started-standalone.md
@@ -1,8 +1,8 @@
---
-id: version-2.10.0-standalone
+id: version-2.10.0-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
[RocksDB](http://rocksdb.org/) and BookKeeper components running inside of a
single Java Virtual Machine (JVM) process.
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 d9c2d382b64..8032f1dc4fe 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
@@ -1,8 +1,8 @@
---
-id: version-2.2.0-standalone
+id: version-2.2.0-getting-started-standalone
title: Setting up a local standalone cluster
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For the purposes of local development and testing, you can run Pulsar in
standalone mode on your own machine. Standalone mode includes a Pulsar broker
as well as the necessary ZooKeeper and BookKeeper components running inside of
a single Java Virtual Machine (JVM) process.
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 e3fe5a8ee08..4062c1538ae 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
@@ -1,8 +1,8 @@
---
-id: version-2.2.1-standalone
+id: version-2.2.1-getting-started-standalone
title: Setting up a local standalone cluster
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For the purposes of local development and testing, you can run Pulsar in
standalone mode on your own machine. Standalone mode includes a Pulsar broker
as well as the necessary ZooKeeper and BookKeeper components running inside of
a single Java Virtual Machine (JVM) process.
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 86c2a3ad8ac..dd49f4aa02b 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
@@ -1,8 +1,8 @@
---
-id: version-2.3.0-standalone
+id: version-2.3.0-getting-started-standalone
title: Setting up a local standalone cluster
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For the purposes of local development and testing, you can run Pulsar in
standalone mode on your own machine. Standalone mode includes a Pulsar broker
as well as the necessary ZooKeeper and BookKeeper components running inside of
a single Java Virtual Machine (JVM) process.
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 7bdeeb8ea52..70d233b8c6a 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
@@ -1,8 +1,8 @@
---
-id: version-2.3.1-standalone
+id: version-2.3.1-getting-started-standalone
title: Setting up a local standalone cluster
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For the purposes of local development and testing, you can run Pulsar in
standalone mode on your own machine. Standalone mode includes a Pulsar broker
as well as the necessary ZooKeeper and BookKeeper components running inside of
a single Java Virtual Machine (JVM) process.
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 1404a2ea5bd..0ff30a18038 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
@@ -1,8 +1,8 @@
---
-id: version-2.3.2-standalone
+id: version-2.3.2-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
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 485d3bebd97..61cf163886d 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
@@ -1,8 +1,8 @@
---
-id: version-2.4.0-standalone
+id: version-2.4.0-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
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 a80f4438443..fda9d90053c 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
@@ -1,8 +1,8 @@
---
-id: version-2.4.1-standalone
+id: version-2.4.1-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
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 2e4e50a02f2..fc5c450fa8f 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
@@ -1,8 +1,8 @@
---
-id: version-2.4.2-standalone
+id: version-2.4.2-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
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 f39a5ffde84..66f22640a39 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
@@ -1,8 +1,8 @@
---
-id: version-2.5.0-standalone
+id: version-2.5.0-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.5.1/concepts-architecture-overview.md
b/site2/website/versioned_docs/version-2.5.1/concepts-architecture-overview.md
index 48cee13cf82..7815c99d3cf 100644
---
a/site2/website/versioned_docs/version-2.5.1/concepts-architecture-overview.md
+++
b/site2/website/versioned_docs/version-2.5.1/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
In a Pulsar instance:
diff --git a/site2/website/versioned_docs/version-2.5.1/standalone.md
b/site2/website/versioned_docs/version-2.5.1/getting-started-standalone.md
similarity index 99%
rename from site2/website/versioned_docs/version-2.5.1/standalone.md
rename to
site2/website/versioned_docs/version-2.5.1/getting-started-standalone.md
index cff185c59a7..949547515b7 100644
--- a/site2/website/versioned_docs/version-2.5.1/standalone.md
+++ b/site2/website/versioned_docs/version-2.5.1/getting-started-standalone.md
@@ -1,8 +1,8 @@
---
-id: version-2.5.1-standalone
+id: version-2.5.1-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
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 76abd7d04ec..280a76a1a5f 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
@@ -1,8 +1,8 @@
---
-id: version-2.6.0-standalone
+id: version-2.6.0-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.6.1/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.6.1/concepts-proxy-sni-routing.md
index 6f7ed80bd55..00d09ddf138 100644
--- a/site2/website/versioned_docs/version-2.6.1/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.6.1/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 33466d952eb..348e0846883 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
@@ -1,8 +1,8 @@
---
-id: version-2.6.1-standalone
+id: version-2.6.1-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.6.2/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.6.2/concepts-proxy-sni-routing.md
index 24ebd361bd7..2fb154acd76 100644
--- a/site2/website/versioned_docs/version-2.6.2/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.6.2/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 66bf840d046..c6c06ba0586 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
@@ -1,8 +1,8 @@
---
-id: version-2.6.2-standalone
+id: version-2.6.2-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.6.3/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.6.3/concepts-proxy-sni-routing.md
index 6d4f88d77b5..ac7fb288fab 100644
--- a/site2/website/versioned_docs/version-2.6.3/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.6.3/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 6218ce8aa18..a25576ea2ee 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
@@ -1,8 +1,8 @@
---
-id: version-2.6.3-standalone
+id: version-2.6.3-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.6.4/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.6.4/concepts-proxy-sni-routing.md
index 97ce3e439c9..58f53ef30f0 100644
--- a/site2/website/versioned_docs/version-2.6.4/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.6.4/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 4a0a43e1aeb..9dc42abd29e 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
@@ -1,8 +1,8 @@
---
-id: version-2.6.4-standalone
+id: version-2.6.4-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.7.0/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.7.0/concepts-proxy-sni-routing.md
index 187796007fb..7375c4c519d 100644
--- a/site2/website/versioned_docs/version-2.7.0/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.7.0/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 69d523ba9cd..3fd3cce4da3 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
@@ -1,8 +1,8 @@
---
-id: version-2.7.0-standalone
+id: version-2.7.0-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.7.1/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.7.1/concepts-proxy-sni-routing.md
index 2c61475b497..f7eac0ee16c 100644
--- a/site2/website/versioned_docs/version-2.7.1/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.7.1/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 d2c33d4ea8a..961194723c9 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
@@ -1,8 +1,8 @@
---
-id: version-2.7.1-standalone
+id: version-2.7.1-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.7.2/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.7.2/concepts-proxy-sni-routing.md
index fd042ad54de..f1b8d956508 100644
--- a/site2/website/versioned_docs/version-2.7.2/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.7.2/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 2019939de29..f18041f41aa 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
@@ -1,8 +1,8 @@
---
-id: version-2.7.2-standalone
+id: version-2.7.2-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.7.3/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.7.3/concepts-proxy-sni-routing.md
index 7685044dbb6..6f9c680b4fa 100644
--- a/site2/website/versioned_docs/version-2.7.3/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.7.3/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 d5f789f3ece..d97bea18dc9 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
@@ -1,8 +1,8 @@
---
-id: version-2.7.3-standalone
+id: version-2.7.3-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.7.4/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.7.4/concepts-proxy-sni-routing.md
index d2b9b06b5df..f2c667a7036 100644
--- a/site2/website/versioned_docs/version-2.7.4/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.7.4/concepts-proxy-sni-routing.md
@@ -45,7 +45,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 3b1193f69b9..b698f6799a3 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
@@ -1,8 +1,8 @@
---
-id: version-2.7.4-standalone
+id: version-2.7.4-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.8.0/concepts-architecture-overview.md
b/site2/website/versioned_docs/version-2.8.0/concepts-architecture-overview.md
index 5ba1fb035e1..a87c774ee7d 100644
---
a/site2/website/versioned_docs/version-2.8.0/concepts-architecture-overview.md
+++
b/site2/website/versioned_docs/version-2.8.0/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
In a Pulsar instance:
diff --git
a/site2/website/versioned_docs/version-2.8.0/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.8.0/concepts-proxy-sni-routing.md
index b7f22d20e49..cffed6d4875 100644
--- a/site2/website/versioned_docs/version-2.8.0/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.8.0/concepts-proxy-sni-routing.md
@@ -44,7 +44,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 01889306c46..ec9512dbbfc 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
@@ -1,8 +1,8 @@
---
-id: version-2.8.0-standalone
+id: version-2.8.0-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.8.1/concepts-architecture-overview.md
b/site2/website/versioned_docs/version-2.8.1/concepts-architecture-overview.md
index f503a3bac1b..b59cdee9ae0 100644
---
a/site2/website/versioned_docs/version-2.8.1/concepts-architecture-overview.md
+++
b/site2/website/versioned_docs/version-2.8.1/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
In a Pulsar instance:
diff --git
a/site2/website/versioned_docs/version-2.8.1/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.8.1/concepts-proxy-sni-routing.md
index 8693d561a2a..0498f3b4173 100644
--- a/site2/website/versioned_docs/version-2.8.1/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.8.1/concepts-proxy-sni-routing.md
@@ -44,7 +44,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 6e6abfb647f..9f9536a55be 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
@@ -1,8 +1,8 @@
---
-id: version-2.8.1-standalone
+id: version-2.8.1-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.8.2/concepts-architecture-overview.md
b/site2/website/versioned_docs/version-2.8.2/concepts-architecture-overview.md
index cbccbe24343..60a0b58a84b 100644
---
a/site2/website/versioned_docs/version-2.8.2/concepts-architecture-overview.md
+++
b/site2/website/versioned_docs/version-2.8.2/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
In a Pulsar instance:
diff --git
a/site2/website/versioned_docs/version-2.8.2/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.8.2/concepts-proxy-sni-routing.md
index 4e95948fcb1..9777fee0825 100644
--- a/site2/website/versioned_docs/version-2.8.2/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.8.2/concepts-proxy-sni-routing.md
@@ -44,7 +44,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 74db78db9a2..89b3925dd18 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
@@ -1,8 +1,8 @@
---
-id: version-2.8.2-standalone
+id: version-2.8.2-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.8.3/concepts-architecture-overview.md
b/site2/website/versioned_docs/version-2.8.3/concepts-architecture-overview.md
index 9bc548c6697..158299c163b 100644
---
a/site2/website/versioned_docs/version-2.8.3/concepts-architecture-overview.md
+++
b/site2/website/versioned_docs/version-2.8.3/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
In a Pulsar instance:
diff --git
a/site2/website/versioned_docs/version-2.8.3/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.8.3/concepts-proxy-sni-routing.md
index 3dec88e0a88..5e9d38a43d2 100644
--- a/site2/website/versioned_docs/version-2.8.3/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.8.3/concepts-proxy-sni-routing.md
@@ -44,7 +44,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
diff --git
a/site2/website/versioned_docs/version-2.8.3/getting-started-standalone.md
b/site2/website/versioned_docs/version-2.8.3/getting-started-standalone.md
index e54b7fc495a..7473674df2d 100644
--- a/site2/website/versioned_docs/version-2.8.3/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.8.3/getting-started-standalone.md
@@ -1,8 +1,8 @@
---
-id: version-2.8.3-standalone
+id: version-2.8.3-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.9.0/concepts-architecture-overview.md
b/site2/website/versioned_docs/version-2.9.0/concepts-architecture-overview.md
index 12ce5364716..7adc9a90a8c 100644
---
a/site2/website/versioned_docs/version-2.9.0/concepts-architecture-overview.md
+++
b/site2/website/versioned_docs/version-2.9.0/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
In a Pulsar instance:
diff --git
a/site2/website/versioned_docs/version-2.9.0/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.9.0/concepts-proxy-sni-routing.md
index 97dcd8e5b31..f214e00c6e3 100644
--- a/site2/website/versioned_docs/version-2.9.0/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.9.0/concepts-proxy-sni-routing.md
@@ -44,7 +44,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 6209f307cc6..d2a136a24ce 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
@@ -1,8 +1,8 @@
---
-id: version-2.9.0-standalone
+id: version-2.9.0-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.9.1/concepts-architecture-overview.md
b/site2/website/versioned_docs/version-2.9.1/concepts-architecture-overview.md
index c81a1e2f4b2..c21e0957a14 100644
---
a/site2/website/versioned_docs/version-2.9.1/concepts-architecture-overview.md
+++
b/site2/website/versioned_docs/version-2.9.1/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
In a Pulsar instance:
diff --git
a/site2/website/versioned_docs/version-2.9.1/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.9.1/concepts-proxy-sni-routing.md
index ab11c772ad9..f0b1fd534f2 100644
--- a/site2/website/versioned_docs/version-2.9.1/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.9.1/concepts-proxy-sni-routing.md
@@ -44,7 +44,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
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 b0dce6ee3d9..f9b7a388d76 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
@@ -1,8 +1,8 @@
---
-id: version-2.9.1-standalone
+id: version-2.9.1-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
diff --git
a/site2/website/versioned_docs/version-2.9.2/concepts-architecture-overview.md
b/site2/website/versioned_docs/version-2.9.2/concepts-architecture-overview.md
index 19bf44e1bf1..7917c6e8008 100644
---
a/site2/website/versioned_docs/version-2.9.2/concepts-architecture-overview.md
+++
b/site2/website/versioned_docs/version-2.9.2/concepts-architecture-overview.md
@@ -46,7 +46,7 @@ Clusters can replicate amongst themselves using
[geo-replication](concepts-repli
## Metadata store
-The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and [BookKeeper
metadata store](https://bookkee [...]
+The Pulsar metadata store maintains all the metadata of a Pulsar cluster, such
as topic metadata, schema, broker load data, and so on. Pulsar uses [Apache
ZooKeeper](https://zookeeper.apache.org/) for metadata storage, cluster
configuration, and coordination. The Pulsar metadata store can be deployed on a
separate ZooKeeper cluster or deployed on an existing ZooKeeper cluster. You
can use one ZooKeeper cluster for both Pulsar metadata store and BookKeeper
metadata store. If you want to d [...]
In a Pulsar instance:
diff --git
a/site2/website/versioned_docs/version-2.9.2/concepts-proxy-sni-routing.md
b/site2/website/versioned_docs/version-2.9.2/concepts-proxy-sni-routing.md
index 922af64b923..d2500943efb 100644
--- a/site2/website/versioned_docs/version-2.9.2/concepts-proxy-sni-routing.md
+++ b/site2/website/versioned_docs/version-2.9.2/concepts-proxy-sni-routing.md
@@ -44,7 +44,7 @@ CONFIG proxy.config.ssl.client.cert.filename STRING
/proxy-key.pem
CONFIG proxy.config.http.connect_ports STRING 4443 6651
```
-The
[ssl_server_name](https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/files/ssl_server_name.yaml.en.html)
file is used to configure TLS connection handling for inbound and outbound
connections. The configuration is determined by the SNI values provided by the
inbound connection. The file consists of a set of configuration items, and each
is identified by an SNI value (`fqdn`). When an inbound TLS connection is made,
the SNI value from the TLS negotiation is matched with the it [...]
+The `ssl_server_name` file is used to configure TLS connection handling for
inbound and outbound connections. The configuration is determined by the SNI
values provided by the inbound connection. The file consists of a set of
configuration items, and each is identified by an SNI value (`fqdn`). When an
inbound TLS connection is made, the SNI value from the TLS negotiation is
matched with the items specified in this file. If the values match, the values
specified in that item override the [...]
The following example shows mapping of the inbound SNI hostname coming from
the client, and the actual broker service URL where request should be
redirected. For example, if the client sends the SNI header `pulsar-broker1`,
the proxy creates a TLS tunnel by redirecting request to the
`pulsar-broker1:6651` service URL.
diff --git
a/site2/website/versioned_docs/version-2.9.2/getting-started-standalone.md
b/site2/website/versioned_docs/version-2.9.2/getting-started-standalone.md
index c2d3128a10d..f497e1a2816 100644
--- a/site2/website/versioned_docs/version-2.9.2/getting-started-standalone.md
+++ b/site2/website/versioned_docs/version-2.9.2/getting-started-standalone.md
@@ -1,8 +1,8 @@
---
-id: version-2.9.2-standalone
+id: version-2.9.2-getting-started-standalone
title: Set up a standalone Pulsar locally
sidebar_label: Run Pulsar locally
-original_id: standalone
+original_id: getting-started-standalone
---
For local development and testing, you can run Pulsar in standalone mode on
your machine. The standalone mode includes a Pulsar broker, the necessary
ZooKeeper and BookKeeper components running inside of a single Java Virtual
Machine (JVM) process.
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 08ca719affd..79116a2ad76 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
@@ -2,7 +2,7 @@
"version-2.1.0-incubating-docs": {
"Getting Started": [
"version-2.1.0-incubating-pulsar-2.0",
- "version-2.1.0-incubating-standalone",
+ "version-2.1.0-incubating-getting-started-standalone",
"version-2.1.0-incubating-getting-started-docker",
"version-2.1.0-incubating-client-libraries"
],
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 8e77c1342a5..6ce02c13d33 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
@@ -2,7 +2,7 @@
"version-2.1.1-incubating-docs": {
"Getting Started": [
"version-2.1.1-incubating-pulsar-2.0",
- "version-2.1.1-incubating-standalone",
+ "version-2.1.1-incubating-getting-started-standalone",
"version-2.1.1-incubating-getting-started-docker",
"version-2.1.1-incubating-client-libraries"
],
diff --git a/site2/website/versioned_sidebars/version-2.10.0-sidebars.json
b/site2/website/versioned_sidebars/version-2.10.0-sidebars.json
index 190e706ae2b..01469e697a6 100644
--- a/site2/website/versioned_sidebars/version-2.10.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.10.0-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.10.0-docs": {
"Get Started": [
- "version-2.10.0-standalone",
+ "version-2.10.0-getting-started-standalone",
"version-2.10.0-getting-started-docker",
"version-2.10.0-getting-started-helm"
],
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 22d5107f83e..3cb98bb1948 100644
--- a/site2/website/versioned_sidebars/version-2.2.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.2.0-sidebars.json
@@ -2,7 +2,7 @@
"version-2.2.0-docs": {
"Getting Started": [
"version-2.2.0-pulsar-2.0",
- "version-2.2.0-standalone",
+ "version-2.2.0-getting-started-standalone",
"version-2.2.0-getting-started-docker",
"version-2.2.0-client-libraries"
],
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 a9f80b94ce0..8dacb7ddb50 100644
--- a/site2/website/versioned_sidebars/version-2.2.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.2.1-sidebars.json
@@ -2,7 +2,7 @@
"version-2.2.1-docs": {
"Getting Started": [
"version-2.2.1-pulsar-2.0",
- "version-2.2.1-standalone",
+ "version-2.2.1-getting-started-standalone",
"version-2.2.1-getting-started-docker",
"version-2.2.1-client-libraries"
],
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 4415ebdba2e..acfea513ee0 100644
--- a/site2/website/versioned_sidebars/version-2.3.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.3.0-sidebars.json
@@ -2,7 +2,7 @@
"version-2.3.0-docs": {
"Getting Started": [
"version-2.3.0-pulsar-2.0",
- "version-2.3.0-standalone",
+ "version-2.3.0-getting-started-standalone",
"version-2.3.0-getting-started-docker",
"version-2.3.0-client-libraries"
],
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 dfe99b5267e..9699030a94a 100644
--- a/site2/website/versioned_sidebars/version-2.3.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.3.1-sidebars.json
@@ -2,7 +2,7 @@
"version-2.3.1-docs": {
"Getting Started": [
"version-2.3.1-pulsar-2.0",
- "version-2.3.1-standalone",
+ "version-2.3.1-getting-started-standalone",
"version-2.3.1-getting-started-docker",
"version-2.3.1-client-libraries"
],
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 b0010379e19..1082676b262 100644
--- a/site2/website/versioned_sidebars/version-2.3.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.3.2-sidebars.json
@@ -2,7 +2,7 @@
"version-2.3.2-docs": {
"Getting Started": [
"version-2.3.2-pulsar-2.0",
- "version-2.3.2-standalone",
+ "version-2.3.2-getting-started-standalone",
"version-2.3.2-getting-started-docker",
"version-2.3.2-client-libraries"
],
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 f340e37ebc1..6c9fb273452 100644
--- a/site2/website/versioned_sidebars/version-2.4.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.4.0-sidebars.json
@@ -2,7 +2,7 @@
"version-2.4.0-docs": {
"Get Started": [
"version-2.4.0-pulsar-2.0",
- "version-2.4.0-standalone",
+ "version-2.4.0-getting-started-standalone",
"version-2.4.0-getting-started-docker",
"version-2.4.0-client-libraries"
],
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 dff09cbdc1f..095bbc2bfc1 100644
--- a/site2/website/versioned_sidebars/version-2.4.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.4.1-sidebars.json
@@ -2,7 +2,7 @@
"version-2.4.1-docs": {
"Get Started": [
"version-2.4.1-pulsar-2.0",
- "version-2.4.1-standalone",
+ "version-2.4.1-getting-started-standalone",
"version-2.4.1-getting-started-docker",
"version-2.4.1-client-libraries"
],
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 78fa7613ab4..52820fe5fb2 100644
--- a/site2/website/versioned_sidebars/version-2.4.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.4.2-sidebars.json
@@ -2,7 +2,7 @@
"version-2.4.2-docs": {
"Get Started": [
"version-2.4.2-pulsar-2.0",
- "version-2.4.2-standalone",
+ "version-2.4.2-getting-started-standalone",
"version-2.4.2-getting-started-docker",
"version-2.4.2-client-libraries"
],
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 fe0880db4b2..302dca6257d 100644
--- a/site2/website/versioned_sidebars/version-2.5.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.5.0-sidebars.json
@@ -2,7 +2,7 @@
"version-2.5.0-docs": {
"Get Started": [
"version-2.5.0-pulsar-2.0",
- "version-2.5.0-standalone",
+ "version-2.5.0-getting-started-standalone",
"version-2.5.0-getting-started-docker",
"version-2.5.0-getting-started-helm",
"version-2.5.0-client-libraries"
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 dcb0cb05efb..5c48e615cb8 100644
--- a/site2/website/versioned_sidebars/version-2.5.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.5.1-sidebars.json
@@ -2,7 +2,7 @@
"version-2.5.1-docs": {
"Get Started": [
"version-2.5.1-pulsar-2.0",
- "version-2.5.1-standalone",
+ "version-2.5.1-getting-started-standalone",
"version-2.5.1-getting-started-docker",
"version-2.5.1-getting-started-helm",
"version-2.5.1-client-libraries"
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 1c804c4494a..13bd0f63050 100644
--- a/site2/website/versioned_sidebars/version-2.5.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.5.2-sidebars.json
@@ -2,7 +2,7 @@
"version-2.5.2-docs": {
"Get Started": [
"version-2.5.2-pulsar-2.0",
- "version-2.5.2-standalone",
+ "version-2.5.2-getting-started-standalone",
"version-2.5.2-getting-started-docker",
"version-2.5.2-getting-started-helm",
"version-2.5.2-client-libraries"
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 a3ee97316f1..1f871c36980 100644
--- a/site2/website/versioned_sidebars/version-2.6.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.0-sidebars.json
@@ -2,7 +2,7 @@
"version-2.6.0-docs": {
"Get Started": [
"version-2.6.0-pulsar-2.0",
- "version-2.6.0-standalone",
+ "version-2.6.0-getting-started-standalone",
"version-2.6.0-getting-started-docker",
"version-2.6.0-getting-started-helm",
"version-2.6.0-client-libraries"
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 5559c46e94d..120c4dbed64 100644
--- a/site2/website/versioned_sidebars/version-2.6.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.1-sidebars.json
@@ -2,7 +2,7 @@
"version-2.6.1-docs": {
"Get Started": [
"version-2.6.1-pulsar-2.0",
- "version-2.6.1-standalone",
+ "version-2.6.1-getting-started-standalone",
"version-2.6.1-getting-started-docker",
"version-2.6.1-getting-started-helm",
"version-2.6.1-client-libraries"
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 3d1b9ca904f..7aab3f2692b 100644
--- a/site2/website/versioned_sidebars/version-2.6.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.2-sidebars.json
@@ -2,7 +2,7 @@
"version-2.6.2-docs": {
"Get Started": [
"version-2.6.2-pulsar-2.0",
- "version-2.6.2-standalone",
+ "version-2.6.2-getting-started-standalone",
"version-2.6.2-getting-started-docker",
"version-2.6.2-getting-started-helm",
"version-2.6.2-client-libraries"
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 09363686011..6f67bfe26a9 100644
--- a/site2/website/versioned_sidebars/version-2.6.3-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.3-sidebars.json
@@ -2,7 +2,7 @@
"version-2.6.3-docs": {
"Get Started": [
"version-2.6.3-pulsar-2.0",
- "version-2.6.3-standalone",
+ "version-2.6.3-getting-started-standalone",
"version-2.6.3-getting-started-docker",
"version-2.6.3-getting-started-helm",
"version-2.6.3-client-libraries"
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 e48382d83fd..3ab1c10d615 100644
--- a/site2/website/versioned_sidebars/version-2.6.4-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.6.4-sidebars.json
@@ -2,7 +2,7 @@
"version-2.6.4-docs": {
"Get Started": [
"version-2.6.4-pulsar-2.0",
- "version-2.6.4-standalone",
+ "version-2.6.4-getting-started-standalone",
"version-2.6.4-getting-started-docker",
"version-2.6.4-getting-started-helm",
"version-2.6.4-client-libraries"
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 a83f2730b5a..eab2fa62b48 100644
--- a/site2/website/versioned_sidebars/version-2.7.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.0-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.7.0-docs": {
"Get Started": [
- "version-2.7.0-standalone",
+ "version-2.7.0-getting-started-standalone",
"version-2.7.0-getting-started-docker",
"version-2.7.0-getting-started-helm"
],
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 c107d8075d9..82e554dc55a 100644
--- a/site2/website/versioned_sidebars/version-2.7.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.1-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.7.1-docs": {
"Get Started": [
- "version-2.7.1-standalone",
+ "version-2.7.1-getting-started-standalone",
"version-2.7.1-getting-started-docker",
"version-2.7.1-getting-started-helm"
],
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 37286a102b5..6acadce6d44 100644
--- a/site2/website/versioned_sidebars/version-2.7.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.2-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.7.2-docs": {
"Get Started": [
- "version-2.7.2-standalone",
+ "version-2.7.2-getting-started-standalone",
"version-2.7.2-getting-started-docker",
"version-2.7.2-getting-started-helm"
],
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 ccbd35054bf..10ad32956de 100644
--- a/site2/website/versioned_sidebars/version-2.7.3-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.3-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.7.3-docs": {
"Get Started": [
- "version-2.7.3-standalone",
+ "version-2.7.3-getting-started-standalone",
"version-2.7.3-getting-started-docker",
"version-2.7.3-getting-started-helm"
],
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 11e38c4888f..ad546ac0bd2 100644
--- a/site2/website/versioned_sidebars/version-2.7.4-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.7.4-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.7.4-docs": {
"Get Started": [
- "version-2.7.4-standalone",
+ "version-2.7.4-getting-started-standalone",
"version-2.7.4-getting-started-docker",
"version-2.7.4-getting-started-helm"
],
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 484a6c99bd1..7ac280ac2c5 100644
--- a/site2/website/versioned_sidebars/version-2.8.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.8.0-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.8.0-docs": {
"Get Started": [
- "version-2.8.0-standalone",
+ "version-2.8.0-getting-started-standalone",
"version-2.8.0-getting-started-docker",
"version-2.8.0-getting-started-helm"
],
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 af2ea682731..b48a29f8158 100644
--- a/site2/website/versioned_sidebars/version-2.8.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.8.1-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.8.1-docs": {
"Get Started": [
- "version-2.8.1-standalone",
+ "version-2.8.1-getting-started-standalone",
"version-2.8.1-getting-started-docker",
"version-2.8.1-getting-started-helm"
],
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 ad0ec10db83..8e23d6ac4aa 100644
--- a/site2/website/versioned_sidebars/version-2.8.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.8.2-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.8.2-docs": {
"Get Started": [
- "version-2.8.2-standalone",
+ "version-2.8.2-getting-started-standalone",
"version-2.8.2-getting-started-docker",
"version-2.8.2-getting-started-helm"
],
diff --git a/site2/website/versioned_sidebars/version-2.8.3-sidebars.json
b/site2/website/versioned_sidebars/version-2.8.3-sidebars.json
index 272781bff58..00dce3ca60f 100644
--- a/site2/website/versioned_sidebars/version-2.8.3-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.8.3-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.8.3-docs": {
"Get Started": [
- "version-2.8.3-standalone",
+ "version-2.8.3-getting-started-standalone",
"version-2.8.3-getting-started-docker",
"version-2.8.3-getting-started-helm"
],
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 a064d049e65..9848b853f80 100644
--- a/site2/website/versioned_sidebars/version-2.9.0-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.9.0-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.9.0-docs": {
"Get Started": [
- "version-2.9.0-standalone",
+ "version-2.9.0-getting-started-standalone",
"version-2.9.0-getting-started-docker",
"version-2.9.0-getting-started-helm"
],
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 28040fa3b52..ee82f0e7c53 100644
--- a/site2/website/versioned_sidebars/version-2.9.1-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.9.1-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.9.1-docs": {
"Get Started": [
- "version-2.9.1-standalone",
+ "version-2.9.1-getting-started-standalone",
"version-2.9.1-getting-started-docker",
"version-2.9.1-getting-started-helm"
],
diff --git a/site2/website/versioned_sidebars/version-2.9.2-sidebars.json
b/site2/website/versioned_sidebars/version-2.9.2-sidebars.json
index c9769eece84..aa67e6d0412 100644
--- a/site2/website/versioned_sidebars/version-2.9.2-sidebars.json
+++ b/site2/website/versioned_sidebars/version-2.9.2-sidebars.json
@@ -1,7 +1,7 @@
{
"version-2.9.2-docs": {
"Get Started": [
- "version-2.9.2-standalone",
+ "version-2.9.2-getting-started-standalone",
"version-2.9.2-getting-started-docker",
"version-2.9.2-getting-started-helm"
],
