- 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.2
- 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
clusterName
is too long (#1229)
TiDB Binlog
- It is recommended that TiDB and Pump be deployed on the same node through the
affinity
feature and Pump be dispersed on different nodes through theanti-affinity
feature. At most only one Pump instance is allowed on each node. We added a guide to the chart. (#1251)
Compatibility
- Fix
tidb-scheduler
RBAC permission in Kubernetes v1.16 (#1282) - Do not set
DNSPolicy
ifhostNetwork
is disabled to keep backward compatibility (#1287)
E2E
- Fix e2e nil point dereference (#1221)
Was this page helpful?