- 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.5 Release Notes
Release date: December 11, 2019
TiDB Operator version: 1.0.5
v1.0.5 What's New
There is no action required if you are upgrading from v1.0.4.
Scheduled Backup
- Fix the issue that backup failed when
clusterNameis too long (#1229)
TiDB Binlog
- It is recommended that TiDB and Pump be deployed on the same node through the
affinityfeature and Pump be dispersed on different nodes through theanti-affinityfeature. At most only one Pump instance is allowed on each node. We added a guide to the chart. (#1251)
Compatibility
- Fix
tidb-schedulerRBAC permission in Kubernetes v1.16 (#1282) - Do not set
DNSPolicyifhostNetworkis disabled to keep backward compatibility (#1287)
E2E
- Fix e2e nil point dereference (#1221)
Was this page helpful?