- 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.2
- v1.1
- v1.0
- v0
TiDB Operator 1.2.0-rc.1 Release Notes
Release date: May 28, 2021
TiDB Operator version: 1.2.0-rc.1
Rolling update changes
- Upgrading TiDB Operator will cause the recreation of the Pump Pod due to #3973
New features
- Support customized labels for TidbCluster Pods and services (#3892, @SabaPing @july2993)
- Support full lifecycle management for Pump (#3973, @july2993)
Improvements
- Mask the backup password in logging (#3979, @dveeden)
- Add an additional volumeMounts field for Grafana (#3960, @mikechengwei)
- Add several useful additional printout columns for TidbMonitor (#3958, @mikechengwei)
- TidbMonitor supports writing monitor configuration to PD etcd directly (#3924, @mikechengwei)
Bug fixes
- Fix the issue that TidbMonitor may not work for DmCluster with TLS enabled (#3991, @csuzhangxc)
- Fix the wrong count of PD members when scaling out PD (#3940, @cvvz)
- Fix the issue that DM-master might fail to restart (#3972, @csuzhangxc)
- Fix the issue that rolling update might happen after changing
configUpdateStrategy
fromInPlace
toRollingUpdate
(#3970, @cvvz) - Fix the issue that backup using Dumpling might fail (#3986, @liubog2008)
Was this page helpful?