Skip to content

improve-access-dashboard-base-on-1.6 #3028

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ti-chi-bot merged 5 commits into from
Dec 10, 2025
Merged

improve-access-dashboard-base-on-1.6 #3028

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
2414eae
improve-access-dashboard-base-on-1.6
yiduoyunQ Dec 1, 2025
8d5c0e0
toml format
yiduoyunQ Dec 10, 2025
55d3ab9
toml format
yiduoyunQ Dec 10, 2025
09b4554
toml format
yiduoyunQ Dec 10, 2025
b811f5b
toml format
yiduoyunQ Dec 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions en/access-dashboard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,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:
Expand Down Expand Up @@ -197,7 +199,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

Expand Down
6 changes: 4 additions & 2 deletions zh/access-dashboard.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,9 @@ metadata:
name: basic
spec:
pd:
enableDashboardInternalProxy: true
config: |
[dashboard]
internal-proxy = true
```

这种方法部署的 TiDB Dashboard，service、port 和 HTTP 路径如下：
Expand Down Expand Up @@ -193,7 +195,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

Expand Down