- 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
- Azure Blob 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.1.12 Release Notes
Release date: April 15, 2021
TiDB Operator version: 1.1.12
New Features
- Support setting customized environment variables for backup and restore job containers (#3833, @dragonly)
- Add additional volume and volumeMount configurations to TidbMonitor (#3855, @mikechengwei)
- The resources in the tidb-operator chart use the new service account when
appendReleaseSuffix
is set totrue
(#3819, @DanielZhangQD)
Improvements
- Add retry for DNS lookup failure exception in TiDBInitializer (#3884, @handlerww)
- Support multiple PVCs for PD during scaling and failover (#3820, @dragonly)
- Optimize the
PodsAreChanged
function (#3901, @shonge)
Bug Fixes
Was this page helpful?