- 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.1.2 Release Notes
Release date: July 1, 2020
TiDB Operator version: 1.1.2
Action Required
- An incompatible issue with PD 4.0.2 has been fixed. Please upgrade TiDB Operator to v1.1.2 before deploying TiDB 4.0.2 and later versions (#2809, @cofyc)
Other Notable Changes
- Collect metrics for TiCDC, TiDB Lightning and TiKV Importer (#2835, @weekface)
- Update PD/TiDB/TiKV config to v4.0.2 (#2828, @DanielZhangQD)
- Fix the bug that
PDMember might still exist after scaling-in (#2793, @Yisaer) - Support Auto-Scaler Reference in
TidbClusterStatus when there existsTidbClusterAutoScaler(#2791, @Yisaer) - Support configuring container lifecycle hooks and
terminationGracePeriodSecondsin TiDB spec (#2810, @weekface)
Was this page helpful?