- Deploy TiDB Cluster
- Deploy Heterogeneous Cluster
- Deploy TiFlash
- Deploy TiCDC
- Deploy TiDB Binlog
- Deploy TiDB Enterprise Edition
- Scale TiDB Cluster
- Backup and Restore
- Use CRDs
- Back up Data to GCS Using Dumpling
- Restore Data from GCS Using TiDB Lightning
- Back up Data to S3-Compatible Storage Using Dumpling
- Restore Data from S3-Compatible Storage Using TiDB Lightning
- Back up Data to GCS Using BR
- Restore Data from GCS Using BR
- Back up Data to S3-Compatible Storage Using BR
- Restore Data from S3-Compatible Storage Using BR
- Use CRDs
- Disaster Recovery
- Release Notes
Based on 1.0, TiDB Operator 1.1 has several new features, including TiDB 4.0 support, TiKV data encryption, and TLS certificate configuration. TiDB Operator v1.1 also supports deploying new components such as TiFlash and TiCDC.
TiDB Operator 1.1 also makes improvements in usability, providing the user experience that is consistent with the Kubernetes native resources.
TidbClusterCR supports deploying and managing the PD Discovery component, which is fully capable of replacing tidb-cluster chart to manage the TiDB cluster.
TidbClusterCR adds support for Pump, TiFlash, TiCDC, and TiDB Dashboard.
Add the Admission Controller (optional) to improve the user experience of upgrade and scaling, and to provide the canary release feature.
tidb-schedulersupports high availability (HA) scheduling at any dimension and scheduler preemption.
Support using tikv-importer chart to deploy and manage tikv-importer.
TidbMonitorCR to deploy the cluster monitoring.
TidbInitializerCR to initialize the cluster.
RestoreCR to back up and restore the cluster, which supports using Amazon S3 or GCS as the remote storage.
Support gracefully restart a component in the TiDB cluster.
Support configuring TLS certificates for the TiDB cluster components and for MySQL clients.
Support TiKV data encryption.
TidbClusterAutoScalerto implement auto-scaling. You can enable this feature by turning on the
Add the optional Advanced StatefulSet Controller, which supports deleting a specific Pod. You can enable this feature by turning on the
For the full release notes, see 1.1 CHANGE LOG.