- 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.1 RC.2 Release Notes
Release date: April 15, 2020
TiDB Operator version: 1.1.0-rc.2
Action Required
- Change TiDB pod
readiness
probe fromHTTPGet
toTCPSocket
4000 port. This will trigger rolling-upgrade for thetidb-server
component. You can setspec.paused
totrue
before upgrading tidb-operator to avoid the rolling upgrade, and set it back tofalse
when you are ready to upgrade your TiDB server (#2139, @weekface)
Notable Changes
- Add
status
field forTidbAutoScaler
CR (#2182, @Yisaer) - Add
spec.pd.maxFailoverCount
field to limit max failover replicas for PD (#2184, @cofyc) - Emit more events for
TidbCluster
andTidbClusterAutoScaler
to help users know TiDB running status (#2150, @Yisaer) - Add the
AGE
column to show creation timestamp for all CRDs (#2168, @cofyc) - Add a switch to skip PD Dashboard TLS configuration (#2143, @weekface)
- Support deploying TiFlash with TidbCluster CR (#2157, @DanielZhangQD)
- Add TLS support for TiKV metrics API (#2137, @weekface)
- Set PD DashboardConfig when TLS between the MySQL client and TiDB server is enabled (#2085, @weekface)
- Remove unnecessary informer caches to reduce the memory footprint of tidb-controller-manager (#1504, @aylei)
- Fix the failure that Helm cannot load the kubeconfig file when deleting the tidb-operator release during
terraform destroy
(#2148, @DanielZhangQD) - Support configuring the Webhook TLS setting by loading a secret (#2135, @Yisaer)
- Support TiFlash in TidbCluster CR (#2122, @DanielZhangQD)
- Fix the error that alertmanager couldn't be set in
TidbMonitor
(#2108, @Yisaer)
What’s on this page
Was this page helpful?