- Introduction
- Get Started
- Deploy
- Deploy TiDB Cluster
- Deploy Heterogeneous Cluster
- Deploy TiFlash
- Deploy TiCDC
- Deploy TiDB Binlog
- Deploy Multiple Sets of TiDB Operator
- Deploy Monitoring
- Secure
- Operate
- Upgrade TiDB Cluster
- Upgrade TiDB Operator
- Perform a Canary Upgrade
- Pause Sync of TiDB Cluster
- Scale TiDB Cluster
- Backup and Restore
- Overview
- Grant Permissions to Remote Storage
- Backup and Restore with S3-Compatible Storage
- Backup and Restore with GCS
- Backup and Restore with Persistent Volumes
- Restart a TiDB Cluster
- Maintain a Kubernetes Node
- View TiDB Logs
- Configure Automatic Failover
- Destroy a TiDB Cluster
- Migrate from Helm 2 to Helm 3
- Disaster Recovery
- Import Data
- Troubleshoot
- FAQs
- Reference
- Architecture
- Sysbench Performance Test
- API References
- Cheat Sheet
- Tools
- Configure
- Log Collection
- Monitoring and Alert on Kubernetes
- Release Notes
- v1.1
- v1.0
- v0
TiDB Operator 1.0.3 Release Notes
Release date: November 13, 2019
TiDB Operator version: 1.0.3
v1.0.3 What's New
Action Required
ACTION REQUIRED: This release upgrades default TiDB version to v3.0.5 which fixed a serious bug in TiDB. So if you are using TiDB v3.0.4 or prior versions, you must upgrade to v3.0.5.
ACTION REQUIRED: This release adds the timezone support for all charts.
For existing TiDB clusters. If the timezone in tidb-cluster/values.yaml has been customized to other timezones instead of the default UTC, then upgrading tidb-operator will trigger a rolling update for the related pods.
The related pods include pump, drainer, discovery, monitor, scheduled backup, tidb-initializer, and tikv-importer.
The time zone for all images maintained by tidb-operator should be UTC. If you use your own images, you need to make sure that the corresponding time zones are UTC.
Improvements
- Add the
timezonesupport for all containers of the TiDB cluster - Support configuring resource requests and limits for all containers of the TiDB cluster