[pulsar] 01/01: [cleanup][doc] Remove deprecated Pulsar Dashboard

[ti...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

tison pushed a commit to branch tisonkun-patch-1
in repository https://gitbox.apache.org/repos/asf/pulsar.git

commit a1ca98d696a7e2a7f26ed955f197661c13c3e5cb
Author: tison <wa...@gmail.com>
AuthorDate: Tue Dec 6 20:35:53 2022 +0800

    [cleanup][doc] Remove deprecated Pulsar Dashboard
    
    This file has been removed from 2.10.x.
    
    Redirections will be added in the site repo later.
---
 site2/docs/administration-dashboard.md | 67 ----------------------------------
 1 file changed, 67 deletions(-)

diff --git a/site2/docs/administration-dashboard.md b/site2/docs/administration-dashboard.md
deleted file mode 100644
index 0bee7be44ce..00000000000
--- a/site2/docs/administration-dashboard.md
+++ /dev/null
@@ -1,67 +0,0 @@
----
-id: administration-dashboard
-title: Pulsar dashboard
-sidebar_label: "Dashboard"
----
-
-:::note
-
-Pulsar dashboard is deprecated. We recommend you use [Pulsar Manager](administration-pulsar-manager.md) to manage and monitor the stats of your topics. 
-
-:::
-
-Pulsar dashboard is a web application that enables users to monitor current stats for all [topics](reference-terminology.md#topic) in tabular form.
-
-The dashboard is a data collector that polls stats from all the brokers in a Pulsar instance (across multiple clusters) and stores all the information in a [PostgreSQL](https://www.postgresql.org/) database.
-
-You can use the [Django](https://www.djangoproject.com) web app to render the collected data.
-
-## Install
-
-The easiest way to use the dashboard is to run it inside a [Docker](https://www.docker.com/products/docker) container.
-
-```shell
-SERVICE_URL=http://broker.example.com:8080/
-docker run -p 80:80 \
--e SERVICE_URL=$SERVICE_URL \
-apachepulsar/pulsar-dashboard:@pulsar:version@
-```
-
-You can find the {@inject: github:Dockerfile:/dashboard/Dockerfile} in the `dashboard` directory and build an image from scratch as well:
-
-```shell
-docker build -t apachepulsar/pulsar-dashboard dashboard
-```
-
-If token authentication is enabled, the provided token should have super-user access. 
-
-```shell
-SERVICE_URL=http://broker.example.com:8080/
-JWT_TOKEN=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
-docker run -p 80:80 \
--e SERVICE_URL=$SERVICE_URL \
--e JWT_TOKEN=$JWT_TOKEN \
-apachepulsar/pulsar-dashboard
-```
- 
-You need to specify only one service URL for a Pulsar cluster. Internally, the collector figures out all the existing clusters and the brokers from where it needs to pull the metrics. If you connect the dashboard to Pulsar running in standalone mode, the URL is `http://<broker-ip>:8080` by default. `<broker-ip>` is the IP address or hostname of the machine that runs Pulsar standalone. The IP address or hostname should be accessible from the running dashboard in the docker instance.
-
-Once the Docker container starts, the web dashboard is accessible via `localhost` or whichever host that the Docker uses.
-
-> The `SERVICE_URL` that the dashboard uses needs to be reachable from inside the Docker container.
-
-If the Pulsar service runs in standalone mode in `localhost`, the `SERVICE_URL` has to
-be the IP address of the machine.
-
-Similarly, given the Pulsar standalone advertises itself with localhost by default, you need to
-explicitly set the advertise address to the host IP address. For example:
-
-```shell
-bin/pulsar standalone --advertised-address 1.2.3.4
-```
-
-:::note
-
-Currently, only Pulsar Token [authentication](security-overview.md#authentication) is supported.
-
-:::
\ No newline at end of file