Thanks to visit codestin.com
Credit goes to github.com

Skip to content

deploy-tiproxy: Fix config section for session tokens #2947

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

deploy-tiproxy: Fix config section for session tokens #2947

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d7d183f
deploy-tiproxy: Fix config section for session tokens
dveeden Oct 6, 2025
bd1a577
Fix links
dveeden Oct 6, 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
7 changes: 4 additions & 3 deletions en/deploy-tiproxy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ summary: Learn how to deploy TiProxy for an existing TiDB cluster on Kubernetes.

# Deploy TiProxy Load Balancer for an Existing TiDB Cluster

This topic describes how to deploy or remove the TiDB load balancer [TiProxy](https://docs.pingcap.com/tidb/v7.6/tiproxy-overview) for an existing TiDB cluster on Kubernetes. TiProxy is placed between the client and TiDB server to provide load balancing, connection persistence, and service discovery for TiDB.
This topic describes how to deploy or remove the TiDB load balancer [TiProxy](https://docs.pingcap.com/tidb/stable/tiproxy-overview) for an existing TiDB cluster on Kubernetes. TiProxy is placed between the client and TiDB server to provide load balancing, connection persistence, and service discovery for TiDB.

> **Note:**
>
Expand Down Expand Up @@ -44,11 +44,11 @@ If you need to deploy TiProxy for an existing TiDB cluster, follow these steps:
level = "info"
```

For more information about TiProxy configuration, see [TiProxy Configuration](https://docs.pingcap.com/tidb/v7.6/tiproxy-configuration).
For more information about TiProxy configuration, see [TiProxy Configuration](https://docs.pingcap.com/tidb/stable/tiproxy-configuration).

4. Configure the related parameters in `spec.tidb` of the TidbCluster CR. For example:

+ It is recommended to configure `graceful-wait-before-shutdown` to a value greater than the maximum duration of the transactions in your application. This is used together with TiProxy's connection migration feature. For more information, see [TiProxy Limitations](https://docs.pingcap.com/tidb/v7.6/tiproxy-overview#limitations).
+ It is recommended to configure `graceful-wait-before-shutdown` to a value greater than the maximum duration of the transactions in your application. This is used together with TiProxy's connection migration feature. For more information, see [TiProxy Limitations](https://docs.pingcap.com/tidb/stable/tiproxy-overview#limitations).

```yaml
spec:
Expand All @@ -70,6 +70,7 @@ If you need to deploy TiProxy for an existing TiDB cluster, follow these steps:
- name: sessioncert
mountPath: /var/session
config: |
[security]
session-token-signing-cert = "/var/session/tls.crt"
session-token-signing-key = "/var/session/tls.key"
```
Expand Down