TiDB onKubernetes
In short: Running TiDB on Kubernetes means using PingCAP's TiDB Operator and its TidbCluster CRD to manage four components: Raft-quorum PD, storage TiKV, and columnar TiFlash as StatefulSets with PersistentVolumeClaims, plus stateless MySQL-compatible TiDB Servers. The operator automates failover, horizontal scaling, rolling upgrades, and BR backups to object storage.
Deploy production-grade TiDB on Kubernetes with TiDB Operator, automated scaling, HTAP analytics, and MySQL-compatible distributed SQL for cloud-native workloads.
Comprehensive TiDB on Kubernetes Services
From TiDB Operator deployment to production HTAP workloads, we provide end-to-end TiDB on Kubernetes solutions for cloud-native distributed SQL environments.
- TiDB Operator installation and CRD setup
- TidbCluster custom resource configuration
- RBAC and namespace isolation
- Multi-cluster operator management
- TiDB Helm chart customization
- Values file tuning for production
- Chart version upgrade strategies
- GitOps integration with ArgoCD / Flux
- PD cluster setup and tuning
- TiKV storage node configuration
- TiDB Server SQL layer deployment
- TiFlash columnar engine setup
- PVC and StorageClass configuration
- Local SSD and cloud block storage
- Separate storage tiers per component
- Volume expansion and snapshots
- TiDB Dashboard deployment
- Prometheus and Grafana setup
- TidbMonitor CRD configuration
- Alertmanager rules and routing
- BR (Backup & Restore) on K8s
- Dumpling logical export setup
- S3-compatible backup storage
- Point-in-time recovery with TiCDC
TiDB Architecture on Kubernetes
Understand how TiDB's distributed components map to Kubernetes primitives, managed by TiDB Operator for a fully automated, cloud-native deployment.
Why Run TiDB on Kubernetes?
TiDB was built for cloud-native environments. Kubernetes provides the ideal platform for operating TiDB's distributed architecture with automated lifecycle management.
Cloud-Native Distributed SQL
TiDB was designed from the ground up as a cloud-native distributed SQL database. On Kubernetes, TiDB Operator manages all components declaratively, integrating seamlessly with your CI/CD pipelines and infrastructure-as-code workflows.
HTAP in a Single Platform
Combine OLTP and OLAP workloads in one database. TiKV handles transactions while TiFlash provides real-time columnar analytics, eliminating the need for separate ETL pipelines and analytics databases.
Elastic Horizontal Scaling
Scale TiDB components independently — add TiKV nodes for more storage, TiDB Servers for more SQL throughput, or TiFlash replicas for faster analytics. All without downtime or manual data rebalancing.
MySQL Compatibility
TiDB speaks the MySQL protocol, so existing MySQL applications, ORMs, and tools work with minimal changes. Migrate from MySQL to TiDB on Kubernetes and gain distributed SQL capabilities without rewriting your application.
TiDB on K8s Key Metrics
Our TiDB on Kubernetes Implementation Process
A proven methodology for deploying production-ready TiDB on Kubernetes with comprehensive testing and validation.
Assessment & Planning
Evaluate your workload requirements, data volume, HTAP needs, and Kubernetes environment. Size PD, TiKV, TiDB Server, and TiFlash components based on throughput and storage targets.
Operator & Cluster Setup
Deploy TiDB Operator via Helm. Configure TidbCluster custom resources, StorageClasses for TiKV and TiFlash, networking, TLS, and resource requests for production readiness.
Migration & Validation
Migrate data from MySQL or other sources using TiDB Lightning or DM (Data Migration). Validate application compatibility, run failover tests, and benchmark OLTP and OLAP performance.
Production & Operations
Go live with TiDB Dashboard monitoring, Prometheus/Grafana alerting, automated BR backups, and runbooks. Provide team training on TiDB Operator management and 24/7 support.
TiDB on Kubernetes — Frequently Asked Questions
Common questions about running TiDB on Kubernetes in production environments.
Related TiDB Services
Explore more ways our TiDB experts can help with your database infrastructure.