Doc Menu

Get Started with TiDB Operator in Kubernetes

This document explains how to create a simple Kubernetes cluster and use it to do a basic test deployment of a TiDB cluster using TiDB Operator.

Warning:

These deployments are for demonstration purposes only. Do not use for qualification or in production!

These are the steps this document follows:

  1. Create a Kubernetes cluster
  2. Deploy TiDB Operator
  3. Deploy a TiDB cluster
  4. Connect to a TiDB cluster

If you have already created a Kubernetes cluster, you can skip to step 2, Deploy TiDB Operator.

If you want to do a production-quality deployment, use one of these resources:

Create a Kubernetes cluster

This section covers 2 different ways to create a simple Kubernetes cluster that can be used to test a TiDB cluster running under TiDB Operator. Choose whichever best matches your environment or experience level.

You can alternatively deploy a Kubernetes cluster in Google Kubernetes Engine in Google Cloud Platform using the Google Cloud Shell, and follow an integrated tutorial to deploy TiDB Operator and the TiDB cluster:

Create a Kubernetes cluster using kind

This section shows how to deploy a Kubernetes cluster using kind.

kind is a tool for running local Kubernetes clusters using Docker containers as cluster nodes. It is developed for testing local Kubernetes clusters. The Kubernetes cluster version depends on the node image that kind uses, and you can specify the image to be used for the nodes and choose any other published version. Refer to Docker Hub to see available tags.

Warning:

This is for demonstration purposes only. Do not use in production!

Before deployment, make sure the following requirements are satisfied:

The following is an example of using kind v0.8.1:

kind create cluster

Expected output:

Creating cluster "kind" ...
 โœ“ Ensuring node image (kindest/node:v1.18.2) ๐Ÿ–ผ
 โœ“ Preparing nodes ๐Ÿ“ฆ
 โœ“ Writing configuration ๐Ÿ“œ
 โœ“ Starting control-plane ๐Ÿ•น๏ธ
 โœ“ Installing CNI ๐Ÿ”Œ
 โœ“ Installing StorageClass ๐Ÿ’พ
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Thanks for using kind! ๐Ÿ˜Š

Check whether the cluster is successfully created:

kubectl cluster-info

Expected output:

Kubernetes master is running at https://127.0.0.1:51026
KubeDNS is running at https://127.0.0.1:51026/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

You're now ready to Deploy TiDB Operator!

To destroy the Kubernetes cluster, run the following command:

kind delete cluster

Create a Kubernetes cluster using minikube

This section describes how to deploy a Kubernetes cluster using minikube.

Minikube can start a local Kubernetes cluster inside a VM on your laptop. It works on macOS, Linux, and Windows.

Warning:

This is for demonstration purposes only. Do not use in production!

Before deployment, make sure the following requirements are satisfied:

  • minikube: version 1.0.0+
    • minikube requires a compatible hypervisor; find more information about that in minikube's installation instructions.
  • kubectl: version >= 1.12

Note:

Although Minikube supports --vm-driver=none that uses host docker instead of VM, it is not fully tested with TiDB Operator and may not work. If you want to try TiDB Operator on a system without virtualization support (e.g., on a VPS), you might consider using kind instead.

Execute the following command to start a minikube Kubernetes cluster:

minikube start

You should see output like this, with some differences depending on your OS and hypervisor:

๐Ÿ˜„  minikube v1.10.1 on Darwin 10.15.4
โœจ  Automatically selected the hyperkit driver. Other choices: docker, vmwarefusion
๐Ÿ’พ  Downloading driver docker-machine-driver-hyperkit:
    > docker-machine-driver-hyperkit.sha256: 65 B / 65 B [---] 100.00% ? p/s 0s
    > docker-machine-driver-hyperkit: 10.90 MiB / 10.90 MiB  100.00% 1.76 MiB p
๐Ÿ”‘  The 'hyperkit' driver requires elevated permissions. The following commands will be executed:

    $ sudo chown root:wheel /Users/user/.minikube/bin/docker-machine-driver-hyperkit
    $ sudo chmod u+s /Users/user/.minikube/bin/docker-machine-driver-hyperkit


๐Ÿ’ฟ  Downloading VM boot image ...
    > minikube-v1.10.0.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s
    > minikube-v1.10.0.iso: 174.99 MiB / 174.99 MiB [] 100.00% 6.63 MiB p/s 27s
๐Ÿ‘  Starting control plane node minikube in cluster minikube
๐Ÿ’พ  Downloading Kubernetes v1.18.2 preload ...
    > preloaded-images-k8s-v3-v1.18.2-docker-overlay2-amd64.tar.lz4: 525.43 MiB
๐Ÿ”ฅ  Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
๐Ÿณ  Preparing Kubernetes v1.18.2 on Docker 19.03.8 ...
๐Ÿ”Ž  Verifying Kubernetes components...
๐ŸŒŸ  Enabled addons: default-storageclass, storage-provisioner
๐Ÿ„  Done! kubectl is now configured to use "minikube"

For Chinese mainland users, you may use local gcr.io mirrors such as registry.cn-hangzhou.aliyuncs.com/google_containers.

minikube start --image-repository registry.cn-hangzhou.aliyuncs.com/google_containers

Or you can configure HTTP/HTTPS proxy environments in your Docker:

# change 127.0.0.1:1086 to your http/https proxy server IP:PORT
minikube start --docker-env https_proxy=http://127.0.0.1:1086 \
  --docker-env http_proxy=http://127.0.0.1:1086

Note:

As minikube is running with VMs (default), the 127.0.0.1 is the VM itself, you might want to use your real IP address of the host machine in some cases.

See minikube setup for more options to configure your virtual machine and Kubernetes cluster.

Execute this command to check the status of your Kubernetes and make sure kubectl can connect to it:

kubectl cluster-info

Expect this output:

Kubernetes master is running at https://192.168.64.2:8443
KubeDNS is running at https://192.168.64.2:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

You're now ready to Deploy TiDB Operator!

To destroy the Kubernetes cluster, run the following command:

minikube delete

Deploy TiDB Operator

Before proceeding, make sure the following requirements are satisfied:

  • A running Kubernetes cluster that kubectl can connect to
  • Helm: Helm 2 (>= Helm 2.16.5) or the latest stable version of Helm 3
  1. Install TiDB Operator CRDs:

    TiDB Operator includes a number of Custom Resource Definitions (CRDs) that implement different components of the TiDB cluster.

    Execute this command to install the CRDs into your cluster:

    kubectl apply -f https://raw.githubusercontent.com/pingcap/tidb-operator/v1.1.2/manifests/crd.yaml

    Expected output:

    customresourcedefinition.apiextensions.k8s.io/tidbclusters.pingcap.com created
    customresourcedefinition.apiextensions.k8s.io/backups.pingcap.com created
    customresourcedefinition.apiextensions.k8s.io/restores.pingcap.com created
    customresourcedefinition.apiextensions.k8s.io/backupschedules.pingcap.com created
    customresourcedefinition.apiextensions.k8s.io/tidbmonitors.pingcap.com created
    customresourcedefinition.apiextensions.k8s.io/tidbinitializers.pingcap.com created
    customresourcedefinition.apiextensions.k8s.io/tidbclusterautoscalers.pingcap.com created
  2. Install TiDB Operator

    The usage of Helm is a little different depending on whether you're using Helm 2 or Helm 3. Check the version of Helm using helm version --short.

    1. If you're using Helm 2, you must set up the server-side component by installing tiller. If you're using Helm 3, skip to the next step.

      Apply the RBAC rule required by the tiller component in the cluster and install tiller:

      kubectl apply -f https://raw.githubusercontent.com/pingcap/tidb-operator/master/manifests/tiller-rbac.yaml && \
      helm init --service-account=tiller --upgrade

      To confirm that the tiller Pod is in the running state, run the following command:

      kubectl get po -n kube-system -l name=tiller

      Expected output:

      NAME                            READY   STATUS    RESTARTS   AGE
      tiller-deploy-b7b9488b5-j6m6p   1/1     Running   0          18s

      Once you see "1/1" in the "READY" column for the "tidb-deploy" pod, go on to the next step.

    2. Add the PingCAP repository:

      helm repo add pingcap https://charts.pingcap.org/

      Expected output:

      "pingcap" has been added to your repositories
    3. Create a namespace for TiDB Operator

      kubectl create namespace tidb-admin

      Expected output:

      namespace/tidb-admin created
    4. Install TiDB Operator

      The helm install syntax is slightly different between Helm 2 and Helm 3.

      • Helm 2:

        helm install --namespace tidb-admin --name tidb-operator pingcap/tidb-operator --version v1.1.2

        If the network connection to the Docker Hub is slow, you can try images hosted in Alibaba Cloud:

        helm install --namespace tidb-admin --name tidb-operator pingcap/tidb-operator --version v1.1.2 \
          --set operatorImage=registry.cn-beijing.aliyuncs.com/tidb/tidb-operator:v1.1.2 \
          --set tidbBackupManagerImage=registry.cn-beijing.aliyuncs.com/tidb/tidb-backup-manager:v1.1.2 \
          --set scheduler.kubeSchedulerImageName=registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler

        Expected output:

        NAME:   tidb-operator
        LAST DEPLOYED: Thu May 28 15:17:38 2020
        NAMESPACE: tidb-admin
        STATUS: DEPLOYED
        
        RESOURCES:
        ==> v1/ConfigMap
        NAME                   DATA  AGE
        tidb-scheduler-policy  1     0s
        
        ==> v1/Deployment
        NAME                     READY  UP-TO-DATE  AVAILABLE  AGE
        tidb-controller-manager  0/1    1           0          0s
        tidb-scheduler           0/1    1           0          0s
        
        ==> v1/Pod(related)
        NAME                                      READY  STATUS             RESTARTS  AGE
        tidb-controller-manager-6d8d5c6d64-b8lv4  0/1    ContainerCreating  0         0s
        tidb-controller-manager-6d8d5c6d64-b8lv4  0/1    ContainerCreating  0         0s
        
        ==> v1/ServiceAccount
        NAME                     SECRETS  AGE
        tidb-controller-manager  1        0s
        tidb-scheduler           1        0s
        
        ==> v1beta1/ClusterRole
        NAME                                   CREATED AT
        tidb-operator:tidb-controller-manager  2020-05-28T22:17:38Z
        tidb-operator:tidb-scheduler           2020-05-28T22:17:38Z
        
        ==> v1beta1/ClusterRoleBinding
        NAME                                   ROLE                                               AGE
        tidb-operator:kube-scheduler           ClusterRole/system:kube-scheduler                  0s
        tidb-operator:tidb-controller-manager  ClusterRole/tidb-operator:tidb-controller-manager  0s
        tidb-operator:tidb-scheduler           ClusterRole/tidb-operator:tidb-scheduler           0s
        tidb-operator:volume-scheduler         ClusterRole/system:volume-scheduler                0s
        
        NOTES:
        Make sure tidb-operator components are running:
        
            kubectl get pods --namespace tidb-admin -l app.kubernetes.io/instance=tidb-operator
      • Helm 3:

        helm install --namespace tidb-admin tidb-operator pingcap/tidb-operator --version v1.1.2

        If the network connection to the Docker Hub is slow, you can try images hosted in Alibaba Cloud:

        helm install --namespace tidb-admin tidb-operator pingcap/tidb-operator --version v1.1.2 \
          --set operatorImage=registry.cn-beijing.aliyuncs.com/tidb/tidb-operator:v1.1.2 \
          --set tidbBackupManagerImage=registry.cn-beijing.aliyuncs.com/tidb/tidb-backup-manager:v1.1.2 \
          --set scheduler.kubeSchedulerImageName=registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler

        Expected output:

        NAME: tidb-operator
        LAST DEPLOYED: Mon Jun  1 12:31:43 2020
        NAMESPACE: tidb-admin
        STATUS: deployed
        REVISION: 1
        TEST SUITE: None
        NOTES:
        Make sure tidb-operator components are running:
        
            kubectl get pods --namespace tidb-admin -l app.kubernetes.io/instance=tidb-operator

      Confirm that the TiDB Operator components are running with this command:

      kubectl get pods --namespace tidb-admin -l app.kubernetes.io/instance=tidb-operator

      Expected output:

      NAME                                       READY   STATUS    RESTARTS   AGE
      tidb-controller-manager-6d8d5c6d64-b8lv4   1/1     Running   0          2m22s
      tidb-scheduler-644d59b46f-4f6sb            2/2     Running   0          2m22s

      As soon as all pods are in the "Running" state, proceed to the next step.

Deploy the TiDB cluster

  1. Deploy the TiDB cluster:

    kubectl create namespace tidb-cluster && \
    curl -LO https://raw.githubusercontent.com/pingcap/tidb-operator/master/examples/basic/tidb-cluster.yaml && \
    kubectl -n tidb-cluster apply -f tidb-cluster.yaml

    If the network connection to the Docker Hub is slow, you can try this example which uses images hosted in Alibaba Cloud:

    kubectl create namespace tidb-cluster && \
    curl -LO https://raw.githubusercontent.com/pingcap/tidb-operator/master/examples/basic-cn/tidb-cluster.yaml && \
    kubectl -n tidb-cluster apply -f tidb-cluster.yaml

    Expected output:

    namespace/tidb-cluster created
    tidbcluster.pingcap.com/basic created
  2. Deploy the TiDB cluster monitor:

    curl -LO https://raw.githubusercontent.com/pingcap/tidb-operator/master/examples/basic/tidb-monitor.yaml && \
    kubectl -n tidb-cluster apply -f tidb-monitor.yaml

    If the network connection to the Docker Hub is slow, you can try this example which uses images hosted in Alibaba Cloud:

    curl -LO https://raw.githubusercontent.com/pingcap/tidb-operator/master/examples/basic-cn/tidb-monitor.yaml && \
    kubectl -n tidb-cluster apply -f tidb-monitor.yaml

    Expected output:

    tidbmonitor.pingcap.com/basic created
  3. View the Pod status:

    watch kubectl get po -n tidb-cluster

    Expected output:

    NAME                              READY   STATUS            RESTARTS   AGE
    basic-discovery-6bb656bfd-kjkxw   1/1     Running           0          29s
    basic-monitor-5fc8589c89-2mwx5    0/3     PodInitializing   0          20s
    basic-pd-0                        1/1     Running           0          29s

    Wait until all pods for all services have been started. As soon as you see pods of each type (-pd, -tikv, and -tidb) and all are in the "Running" state, you can hit Ctrl-C to get back to the command line and go on to connect to your TiDB cluster!

    Expected output:

    NAME                              READY   STATUS    RESTARTS   AGE
    basic-discovery-6bb656bfd-xl5pb   1/1     Running   0          9m9s
    basic-monitor-5fc8589c89-gvgjj    3/3     Running   0          8m58s
    basic-pd-0                        1/1     Running   0          9m8s
    basic-tidb-0                      2/2     Running   0          7m14s
    basic-tikv-0                      1/1     Running   0          8m13s

Connect to TiDB

  1. Install mysql command-line client

    To connect to TiDB, you'll need a MySQL-compatible command-line client installed on the host where you've used kubectl. This can be the mysql executable from an installation of MySQL Server, MariaDB Server, Percona Server, or a standalone client executable from your operating system's package repository.

    Note:

    • To connect to TiDB using a MySQL client from MySQL 8.0, you must explicitly specify --default-auth=mysql_native_password if the user account has a password, because mysql_native_password is no longer the default plugin.
  2. Forward port 4000

    You can connect to TiDB by first forwarding a port from the local host to the TiDB service in Kubernetes. First, get a list of services in the tidb-cluster namespace:

    kubectl get svc -n tidb-cluster

    Expected output:

    NAME                     TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)              AGE
    basic-discovery          ClusterIP   10.101.69.5      <none>        10261/TCP            10m
    basic-grafana            ClusterIP   10.106.41.250    <none>        3000/TCP             10m
    basic-monitor-reloader   ClusterIP   10.99.157.225    <none>        9089/TCP             10m
    basic-pd                 ClusterIP   10.104.43.232    <none>        2379/TCP             10m
    basic-pd-peer            ClusterIP   None             <none>        2380/TCP             10m
    basic-prometheus         ClusterIP   10.106.177.227   <none>        9090/TCP             10m
    basic-tidb               ClusterIP   10.99.24.91      <none>        4000/TCP,10080/TCP   8m40s
    basic-tidb-peer          ClusterIP   None             <none>        10080/TCP            8m40s
    basic-tikv-peer          ClusterIP   None             <none>        20160/TCP            9m39s

    In this case, the TiDB service is called basic-tidb. Use kubectl to forward this port from the local host to the cluster service:

    kubectl port-forward -n tidb-cluster svc/basic-tidb 4000 > pf4000.out &

    This command runs in the background and writes its output to a file called pf4000.out so we can continue working in the same shell session.

  3. Connect to TiDB

    mysql -h 127.0.0.1 -P 4000 -u root

    Expected output:

    Welcome to the MySQL monitor.  Commands end with ; or \g.
    Your MySQL connection id is 76
    Server version: 5.7.25-TiDB-v4.0.0 MySQL Community Server (Apache License 2.0)
    
    Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.
    
    Oracle is a registered trademark of Oracle Corporation and/or its
    affiliates. Other names may be trademarks of their respective
    owners.
    
    Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
    
    mysql>

    Here are some commands you can execute after connecting to the cluster to see some of the functionality available in TiDB. (Some of these require TiDB 4.0; if you've deployed an earlier version, upgrade by consulting the Upgrade the TiDB cluster section).

    mysql> create table hello_world (id int unsigned not null auto_increment primary key, v varchar(32));
    Query OK, 0 rows affected (0.17 sec)
    
    mysql> select * from information_schema.tikv_region_status where db_name=database() and table_name='hello_world'\G
    *************************** 1. row ***************************
           REGION_ID: 2
           START_KEY: 7480000000000000FF3700000000000000F8
             END_KEY:
            TABLE_ID: 55
             DB_NAME: test
          TABLE_NAME: hello_world
            IS_INDEX: 0
            INDEX_ID: NULL
          INDEX_NAME: NULL
      EPOCH_CONF_VER: 5
       EPOCH_VERSION: 23
       WRITTEN_BYTES: 0
          READ_BYTES: 0
    APPROXIMATE_SIZE: 1
    APPROXIMATE_KEYS: 0
    1 row in set (0.03 sec)
    mysql> select tidb_version()\G
    *************************** 1. row ***************************
    tidb_version(): Release Version: v4.0.0
    Edition: Community
    Git Commit Hash: 689a6b6439ae7835947fcaccf329a3fc303986cb
    Git Branch: heads/refs/tags/v4.0.0
    UTC Build Time: 2020-05-28 01:37:40
    GoVersion: go1.13
    Race Enabled: false
    TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
    Check Table Before Drop: false
    1 row in set (0.00 sec)
    mysql> select * from information_schema.tikv_store_status\G
    *************************** 1. row ***************************
             STORE_ID: 4
              ADDRESS: basic-tikv-0.basic-tikv-peer.tidb-cluster.svc:20160
          STORE_STATE: 0
     STORE_STATE_NAME: Up
                LABEL: null
              VERSION: 4.0.0
             CAPACITY: 58.42GiB
            AVAILABLE: 36.18GiB
         LEADER_COUNT: 3
        LEADER_WEIGHT: 1
         LEADER_SCORE: 3
          LEADER_SIZE: 3
         REGION_COUNT: 21
        REGION_WEIGHT: 1
         REGION_SCORE: 21
          REGION_SIZE: 21
             START_TS: 2020-05-28 22:48:21
    LAST_HEARTBEAT_TS: 2020-05-28 22:52:01
               UPTIME: 3m40.598302151s
    1 rows in set (0.01 sec)
    mysql> select * from information_schema.cluster_info\G
    *************************** 1. row ***************************
              TYPE: tidb
          INSTANCE: basic-tidb-0.basic-tidb-peer.tidb-cluster.svc:4000
    STATUS_ADDRESS: basic-tidb-0.basic-tidb-peer.tidb-cluster.svc:10080
           VERSION: 5.7.25-TiDB-v4.0.0
          GIT_HASH: 689a6b6439ae7835947fcaccf329a3fc303986cb
        START_TIME: 2020-05-28T22:50:11Z
            UPTIME: 3m21.459090928s
    *************************** 2. row ***************************
              TYPE: pd
          INSTANCE: basic-pd:2379
    STATUS_ADDRESS: basic-pd:2379
           VERSION: 4.0.0
          GIT_HASH: 56d4c3d2237f5bf6fb11a794731ed1d95c8020c2
        START_TIME: 2020-05-28T22:45:04Z
            UPTIME: 8m28.459091915s
    *************************** 3. row ***************************
              TYPE: tikv
          INSTANCE: basic-tikv-0.basic-tikv-peer.tidb-cluster.svc:20160
    STATUS_ADDRESS: 0.0.0.0:20180
           VERSION: 4.0.0
          GIT_HASH: 198a2cea01734ce8f46d55a29708f123f9133944
        START_TIME: 2020-05-28T22:48:21Z
            UPTIME: 5m11.459102648s
    3 rows in set (0.01 sec)
  4. Load Grafana dashboard

    As done above for port 4000 to the TiDB service, also forward the port for Grafana so we can load the monitoring dashboard:

    kubectl port-forward -n tidb-cluster svc/basic-grafana 3000 > pf3000.out &

    The dashboard will be accessible at http://localhost:3000 on the host where you've run kubectl. Note that if you're running kubectl in a Docker container or on a remote host, you may not be able to load this URL and additional networking beyond the scope of this document may be necessary.

    The default username and password in Grafana are both "admin".

    For more information about monitoring the TiDB cluster in TiDB Operator, consult Monitor a TiDB Cluster Using TidbMonitor.

Upgrade the TiDB cluster

TiDB Operator also makes it easy to perform a rolling upgrade of the TiDB cluster. If you've deployed TiDB 3.0 or TiDB 3.1 using TiDB Operator, you can perform an online upgrade to TiDB 4.0.

In this example, you will upgrade the TiDB cluster to the "nightly" release.

Kubernetes makes it possible to both "edit" and "patch" deployed resources.

kubectl edit opens a resource specification in an interactive text editor, where an administrator can make changes and save them. If the changes are valid, they'll be propagated to the cluster resources; if they're invalid, they'll be rejected with an error message. Note that not all elements of the specification are validated at this time; it's possible to save changes that may not be applied to the cluster even though they're accepted.

kubectl patch applies a specification change directly to the running cluster resources. There are several different patch strategies, each of which has various capabilities, limitations, and allowed formats.

  1. Patch the TidbCluster resource

    In this case, we can use a JSON merge patch to update the version of the TiDB cluster to "nightly":

    kubectl patch tc basic -n tidb-cluster --type merge -p '{"spec": {"version": "release-4.0-nightly"} }'

    Expected output:

    tidbcluster.pingcap.com/basic patched
  2. Wait for all pods to restart

    Execute this command to follow the progress of the cluster as its components are upgraded. You should see some pods transition to "Terminating" and then back to "ContainerCreating" and back to "Running". Note the value in the "AGE" pod column to see which pods have restarted.

    watch kubectl get po -n tidb-cluster

    Expected output:

    NAME                              READY   STATUS        RESTARTS   AGE
    basic-discovery-6bb656bfd-7lbhx   1/1     Running       0          24m
    basic-pd-0                        1/1     Terminating   0          5m31s
    basic-tidb-0                      2/2     Running       0          2m19s
    basic-tikv-0                      1/1     Running       0          4m13s
  3. Forward port

    After all pods have been restarted, you should be able to see that the version number of the cluster has changed. Note that any port forwarding you set up in a previous step will need to be re-done, because the pod(s) they forwarded to will have been destroyed and re-created. If the kubectl port-forward process is still running in your shell, kill it before forwarding the port again.

    kubectl port-forward -n tidb-cluster svc/basic-tidb 4000 > pf4000.out &
  4. Check the version of the TiDB cluster

    mysql -h 127.0.0.1 -P 4000 -u root -e 'select tidb_version()\G'

    Expected output:

    *************************** 1. row ***************************
    tidb_version(): Release Version: v4.0.0-6-gdec49a126
    Edition: Community
    Git Commit Hash: dec49a12654c4f09f6fedfd2a0fb0154fc095449
    Git Branch: release-4.0
    UTC Build Time: 2020-06-01 10:07:32
    GoVersion: go1.13
    Race Enabled: false
    TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
    Check Table Before Drop: false

For more details about upgrading the TiDB cluster running in TiDB Operator, refer to Upgrade the TiDB cluster.

Destroy the TiDB cluster

After you've finished testing, you may wish to destroy the TiDB cluster.

Instructions for destroying the Kubernetes clusters depend on where the Kubernetes cluster is running and how it was created, so refer to those sections for more details. The following steps will destroy the TiDB cluster, but will not affect the Kubernetes cluster itself.

  1. Delete the TiDB cluster:

    kubectl delete tc basic -n tidb-cluster
  2. Delete TiDB Monitor:

    kubectl delete tidbmonitor basic -n tidb-cluster
  3. Delete persistent data

    If your deployment has persistent data storage, deleting the TiDB cluster will not remove the cluster's data. If you do not need the data anymore, you should run the following commands to clean the data and the dynamically created persistent disks:

    kubectl delete pvc -n tidb-cluster -l app.kubernetes.io/instance=basic,app.kubernetes.io/managed-by=tidb-operator && \
    kubectl get pv -l app.kubernetes.io/namespace=tidb-cluster,app.kubernetes.io/managed-by=tidb-operator,app.kubernetes.io/instance=basic -o name | xargs -I {} kubectl patch {} -p '{"spec":{"persistentVolumeReclaimPolicy":"Delete"}}'
  4. Delete namespaces

    To make sure there are no lingering resources, you can delete the namespace used for your TiDB cluster.

    kubectl delete namespace tidb-cluster
  5. Stop kubectl port forwarding

    If you still have running kubectl processes that are forwarding ports, end them.

    pgrep -lfa kubectl

For more information about destroying a TiDB cluster running in TiDB Operator, consult Destroy a TiDB Cluster.