TiDB Operator
The official Kubernetes operator for TiDB — automates deploying, scaling, upgrading, and managing TiDB clusters as cloud-native workloads.
TiDB Operator manages the full lifecycle of a TiDB cluster on Kubernetes — provisioning PD, TiKV, and TiDB components, handling rolling upgrades and scaling, automating backup and restore, and integrating with Kubernetes-native monitoring. It’s installed via an official Helm chart and is how most self-managed TiDB clusters are run in production rather than deploying the components by hand.
It’s developed by PingCAP under the Apache 2.0 license, with documentation available in English and Simplified Chinese. The project’s main branch tracks the newer v2 line of the operator, alongside a maintained release-1.x branch for the earlier v1 API.
Community feedback
This space is for grounded, evaluable experience — versions used, environments, what you measured or observed, and how it behaves alongside other software. General impressions without supporting detail may be removed. Sign in to write one; posts are tied to a verified identity, not anonymous.