- 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.2.4 Release Notes
Release date: October 21, 2021
TiDB Operator version: 1.2.4
Rolling update changes
- Upgrading TiDB Operator will cause the recreation of the TiDBMonitor Pod due to #4180
New features
- TidbMonitor supports customizing prometheus rules and reloading configurations dynamically (#4180, @mikechengwei)
- TidbMonitor supports the
enableRules
field. When AlertManager is not configured, you can configure this field totrue
to add Prometheus rules (#4115, @mikechengwei)
Improvements
- Optimize
TiFlash
rolling upgrade process (#4193, @KanShiori) - Support deleting backup data in batches (#4095, @KanShiori)
Bug fixes
- Fix the security vulnerabilities in the
tidb-backup-manager
andtidb-operator
images (#4217, @KanShiori) - Fix the issue that some backup data might retain if the
Backup
CR is deleted when theBackup
job is running (#4133, @KanShiori)
Was this page helpful?