- Introduction
- Get Started
- Deploy
- In Self-Managed Kubernetes
- In Public Cloud Kubernetes
- Deploy TiDB on ARM64 Machines
- Deploy TiFlash to Explore TiDB HTAP
- Deploy TiDB Across Multiple Kubernetes Clusters
- Deploy a Heterogeneous TiDB Cluster
- Deploy TiCDC
- Deploy TiDB Binlog
- Monitor and Alert
- Migrate
- Import Data
- Migrate from MySQL
- Migrate TiDB to Kubernetes
- Manage
- Secure
- Scale
- Upgrade
- Upgrade a TiDB Cluster
- Upgrade TiDB Operator
- Backup and Restore
- Overview
- Backup and Restore Custom Resources
- Grant Permissions to Remote Storage
- Amazon S3 Compatible Storage
- Google Cloud Storage
- Persistent Volumes
- Maintain
- Restart a TiDB Cluster
- Destroy a TiDB Cluster
- View TiDB Logs
- Modify TiDB Cluster Configuration
- Configure Automatic Failover
- Pause Sync of TiDB Cluster
- Maintain Different TiDB Clusters Separately Using Multiple TiDB Operator
- Maintain Kubernetes Nodes
- Migrate from Helm 2 to Helm 3
- Replace Nodes for a TiDB Cluster
- Disaster Recovery
- Troubleshoot
- FAQs
- Reference
- Release Notes
- v1.3
- v1.2
- v1.1
- v1.0
- v0
TiDB Operator 1.2.0-alpha.1 Release Notes
Release date: January 15, 2021
TiDB Operator version: 1.2.0-alpha.1
Rolling Update Changes
- Due to #3440, the Pod of TidbMonitor will be deleted and recreated after TiDB Operator is upgraded to v1.2.0-alpha.1.
New Features
- Deploy one TiDB cluster across multiple Kubernetes clusters (@L3T, @handlerww)
- Support DM 2.0 in TiDB Operator (@lichunzhu, @BinChenn)
- Auto-Scaling with PD API (@howardlau1999)
- Canary Upgrade of TiDB Operator (#3548, @shonge, #3554, @cvvz)
Improvements
- Add local backend support for the TiDB Lightning chart (#3644, @csuzhangxc)
- Add TLS support for the TiDB Lightning chart and TiKV Importer chart (#3598, @csuzhangxc)
- Support persisting checkpoint for TiDB Lightning helm chart (#3653, @csuzhangxc)
- Support Thanos sidecar for monitoring multiple clusters (#3579, @mikechengwei)
- Migrate from Deployment to StatefulSet for TidbMonitor (#3440, @mikechengwei)
Other Notable Changes
- Optimize rate limiter intervals (#3700, @dragonly)
- Change the directory to save the customized alert rules in TidbMonitor from
tidb:${tidb_image_version}
totidb:${initializer_image_version}
. Please note that if thespec.initializer.version
in the TidbMonitor does not match with the TiDB version in the TidbCluster, upgrading TiDB Operator will cause the re-creation of the monitor Pod (#3684, @BinChenn)
Was this page helpful?