improve-access-dashboard-base-on-1.6 (#3028) (#3032)

Author: ti-chi-bot

en/access-dashboard.md

@@ -41,7 +41,9 @@ metadata:
   name: basic
 spec:
   pd:
-    enableDashboardInternalProxy: true
+    config: |
+      [dashboard]
+        internal-proxy = true
 ```
 
 In this deployment method, the `service`, `port`, and `HTTP` paths of TiDB Dashboard are as follows:
@@ -196,7 +198,7 @@ spec:
 
 After deploying the `Service`, you can access TiDB Dashboard via <https://{nodeIP}:{nodePort}/dashboard>. By default, `nodePort` is randomly assigned by Kubernetes. You can also specify an available port in the `.yaml` file.
 
-Note that if there is more than one PD `Pod` in the cluster, you need to set `spec.pd.enableDashboardInternalProxy: true` in the `TidbCluster` CR to ensure normal access to TiDB Dashboard.
+Note that if there is more than one PD `Pod` in the cluster, you need to set `spec.pd.config.dashboard.internal-proxy: true` in the `TidbCluster` CR to ensure normal access to TiDB Dashboard.
 
 ### Access independently deployed TiDB Dashboard
 

zh/access-dashboard.md

@@ -37,7 +37,9 @@ metadata:
   name: basic
 spec:
   pd:
-    enableDashboardInternalProxy: true
+    config: |
+      [dashboard]
+        internal-proxy = true
 ```
 
 这种方法部署的 TiDB Dashboard，service、port 和 HTTP 路径如下：
@@ -192,7 +194,7 @@ spec:
 
 当 `Service` 部署完成后，可以通过 `https://{nodeIP}:{nodePort}/dashboard` 访问 TiDB Dashboard, 其中 `nodePort` 默认由 Kubernetes 随机分配，也可以在 yaml 文件中指定一个可用的端口。
 
-需要注意如果 PD Pod 数量超过 1 ，需要在 TidbCluster CR 中设置 `spec.pd.enableDashboardInternalProxy: true` 以保证正常访问 TiDB Dashboard。
+需要注意如果 PD Pod 数量超过 1 ，需要在 TidbCluster CR 中设置 `spec.pd.config.dashboard.internal-proxy: true` 以保证正常访问 TiDB Dashboard。
 
 ### 访问独立部署的 TiDB Dashboard