update helm deploy (apache#8404)

site2/website/versioned_docs/version-2.6.1/helm-deploy.md

@@ -328,8 +328,7 @@ cd pulsar/deployment/kubernetes/helm
 
 The `prepare_helm_release` creates the following resources:
 
-- A Kubernetes namespace for installing the Pulsar release
-- A secret for storing the username and password of the control center administrator. The username and password can be passed to `prepare_helm_release.sh` through flags `--control-center-admin` and `--control-center-password`. The username and password is used for logging into the Grafana dashboard and Pulsar Manager.
+- A Kubernetes namespace for installing the Pulsar release.
 - JWT secret keys and tokens for three super users: `broker-admin`, `proxy-admin`, and `admin`. By default, it generates an asymmetric pubic/private key pair. You can choose to generate a symmetric secret key by specifying `--symmetric`.
     - `proxy-admin` role is used for proxies to communicate to brokers.
     - `broker-admin` role is used for inter-broker communications.

site2/website/versioned_docs/version-2.6.2/helm-deploy.md

@@ -329,7 +329,6 @@ cd pulsar/deployment/kubernetes/helm
 The `prepare_helm_release` creates the following resources:
 
 - A Kubernetes namespace for installing the Pulsar release
-- A secret for storing the username and password of the control center administrator. The username and password can be passed to `prepare_helm_release.sh` through flags `--control-center-admin` and `--control-center-password`. The username and password is used for logging into the Grafana dashboard and Pulsar Manager.
 - JWT secret keys and tokens for three super users: `broker-admin`, `proxy-admin`, and `admin`. By default, it generates an asymmetric pubic/private key pair. You can choose to generate a symmetric secret key by specifying `--symmetric`.
     - `proxy-admin` role is used for proxies to communicate to brokers.
     - `broker-admin` role is used for inter-broker communications.