概要

フル名
docker.io/pingcap/tiproxy
Registry
docker.io
名前空間
pingcap
リポジトリ
tiproxy
キャッシュ Tag 数
562
最終同期
07/06/2026, 05:42 PM

概要

TiDB TiProxy 连接代理镜像,在应用与 TiDB 集群间做会话保持、流量切分与故障转移,降低数据库扩缩容对客户端的影响。

詳細

pingcap/tiproxy 实现 TiDB 官方中间层代理,客户端 JDBC/MySQL 协议连 TiProxy 而非直连 tidb-server,由代理根据路由规则转发至后端节点。与 HAProxy 通用 TCP 代理相比理解 TiDB 拓扑与健康检查,支持 smooth migration 与 read/write 分离策略。生产需配置 backend 地址列表、TLS 与连接池上限;通常与 TiDB Operator 同集群部署,监控 QPS 与 backend 切换事件。

快速启动

docker run -d --name tiproxy \
  -p 6000:6000 \
  -e TIPROXY_BACKEND=tidb-pd:2379 \
  docker.io/pingcap/tiproxy:latest

推荐实践

docker run -d --name tiproxy \
  --restart unless-stopped \
  -p 6000:6000 \
  -v /data/tiproxy:/etc/tiproxy \
  -e TIPROXY_CONFIG=/etc/tiproxy/tiproxy.toml \
  docker.io/pingcap/tiproxy:v1.0.0

核心参数说明

  • -p 6000:6000 — MySQL 协议代理端口
  • -v /data/tiproxy:/etc/tiproxy — tiproxy.toml 路由配置
  • -e TIPROXY_CONFIG — 主配置文件路径
  • --restart unless-stopped — 数据库入口层高可用
  • 固定 tag — 与 TiDB 集群版本匹配
  • 配对 — 需已部署 TiDB/tidb-server 后端

Kubernetes

apiVersion: apps/v1
kind: Deployment
metadata:
  name: tiproxy
spec:
  replicas: 2
  selector:
    matchLabels:
      app: tiproxy
  template:
    metadata:
      labels:
        app: tiproxy
    spec:
      containers:
        - name: tiproxy
          image: docker.io/pingcap/tiproxy:v1.0.0
          ports:
            - containerPort: 6000
          volumeMounts:
            - name: config
              mountPath: /etc/tiproxy
      volumes:
        - name: config
          configMap:
            name: tiproxy-config
---
apiVersion: v1
kind: Service
metadata:
  name: tiproxy
spec:
  selector:
    app: tiproxy
  ports:
    - port: 6000
      targetPort: 6000

tiproxy.toml 经 ConfigMap 挂载;应用 JDBC 指向 tiproxy Service,与 TiDB Operator 生成的 tidb 地址协调路由规则。

Tagアーキテクチャプッシュ日時サイズDigest同期期望操作
docker.io/pingcap/tiproxy
:v1.3.3-beta.2
linux/arm64linux/amd64
2026/06/30 10:07178.6 MBsha256:9722cb21e065
docker.io/pingcap/tiproxy
:main
linux/arm64linux/amd64
2026/06/23 22:41178.5 MBsha256:34f7ea6c452d
docker.io/pingcap/tiproxy
:main-1e326b0
linux/arm64linux/amd64
2026/06/23 22:41178.5 MBsha256:34f7ea6c452d
docker.io/pingcap/tiproxy
:main-1e326b0_linux_arm64
linux/arm64
2026/06/23 22:41178.5 MBsha256:34f7ea6c452d
docker.io/pingcap/tiproxy
:main-1e326b0_linux_amd64
linux/amd64
2026/06/23 22:40184.3 MBsha256:076d25670c82
docker.io/pingcap/tiproxy
:main-56a7f03
linux/arm64linux/amd64
2026/06/22 18:15178.5 MBsha256:4536f96ce3fc
docker.io/pingcap/tiproxy
:main-56a7f03_linux_arm64
linux/arm64
2026/06/22 18:15178.5 MBsha256:4536f96ce3fc
docker.io/pingcap/tiproxy
:main-56a7f03_linux_amd64
linux/amd64
2026/06/22 18:12184.2 MBsha256:14ef0d7200d0
docker.io/pingcap/tiproxy
:main-b02569c
linux/arm64linux/amd64
2026/06/22 17:16178.5 MBsha256:f75bdf824717
docker.io/pingcap/tiproxy
:main-b02569c_linux_arm64
linux/arm64
2026/06/22 17:16178.5 MBsha256:f75bdf824717
docker.io/pingcap/tiproxy
:main-b02569c_linux_amd64
linux/amd64
2026/06/22 17:15184.2 MBsha256:1e71ca0aefb5
docker.io/pingcap/tiproxy
:main-9fafc2f
linux/amd64linux/arm64
2026/06/15 11:02184.2 MBsha256:a99e21cd676b
docker.io/pingcap/tiproxy
:main-9fafc2f_linux_amd64
linux/amd64
2026/06/15 11:02184.2 MBsha256:a99e21cd676b
docker.io/pingcap/tiproxy
:main-9fafc2f_linux_arm64
linux/arm64
2026/06/15 11:02178.5 MBsha256:8647fd789bf0
docker.io/pingcap/tiproxy
:v26.3.1
linux/arm64linux/amd64
2026/06/08 15:16163.3 MBsha256:6d7dc09c8d33
docker.io/pingcap/tiproxy
:main-9798547
linux/amd64linux/arm64
2026/06/04 16:07168.9 MBsha256:a2391b9893ab
docker.io/pingcap/tiproxy
:main-9798547_linux_amd64
linux/amd64
2026/06/04 16:07168.9 MBsha256:a2391b9893ab
docker.io/pingcap/tiproxy
:main-9798547_linux_arm64
linux/arm64
2026/06/04 16:06163.3 MBsha256:a060840bf5f2
docker.io/pingcap/tiproxy
:main-99915da
linux/amd64linux/arm64
2026/05/30 01:10168.9 MBsha256:eb3edd02d105
docker.io/pingcap/tiproxy
:main-99915da_linux_amd64
linux/amd64
2026/05/30 01:10168.9 MBsha256:eb3edd02d105