This document describes how to deploy a TiDB cluster on general Kubernetes.
Use the following commands to get the
values.yaml configuration file of the tidb-cluster chart to be deployed.
mkdir -p /home/tidb/<release-name> && \ helm inspect values pingcap/tidb-cluster --version=<chart-version> > /home/tidb/<release-name>/values-<release-name>.yaml
The TiDB cluster uses
local-storage by default.
- For the production environment, local storage is recommended. The actual local storage in Kubernetes clusters might be sorted by disk types, such as
- For the demonstration environment or functional verification, you can use network storage, such as
Different components of a TiDB cluster have different disk requirements. Before deploying a TiDB cluster, select the appropriate storage class for each component according to the storage classes supported by the current Kubernetes cluster and usage scenario. You can set the storage class by modifying
storageClassName of each component in
values.yaml. For the storage classes supported by the Kubernetes cluster, check with your system administrator.
The deployed cluster topology by default has 3 PD Pods, 3 TiKV Pods, 2 TiDB Pods, and 1 Monitor Pod. In this deployment topology, the scheduler extender of TiDB Operator requires at least 3 nodes in the Kubernetes cluster to provide high availability. If the number of Kubernetes cluster nodes is less than 3, 1 PD Pod goes to the Pending state, and neither TiKV Pods nor TiDB Pods are created.
When the number of nodes in the Kubernetes cluster is less than 3, to start the TiDB cluster, you can reduce both the number of PD Pods and TiKV Pods in the default deployment to
1, or modify the
default-scheduler, a built-in scheduler in Kubernetes.
For more configuration parameters, see TiDB cluster configurations in Kubernetes.
After you deploy and configure TiDB Operator, deploy the TiDB cluster using the following commands:
helm install pingcap/tidb-cluster --name=<release-name> --namespace=<namespace> --version=<chart-version> -f /home/tidb/<release-name>/values-<release-name>.yaml
You can view the Pod status using the following command:
kubectl get po -n <namespace> -l app.kubernetes.io/instance=<release-name>
You can use TiDB Operator to deploy and manage multiple sets of TiDB clusters in a single Kubernetes cluster by repeating the above command and replacing
release-name with a different name. Different clusters can be in the same or different
namespace. You can select different clusters according to your actual needs.