# TiDB Operator Release Notes > This document lists all released TiDB Operator versions, sorted by version number in descending order. - v2.0 - [2.0 GA](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-2.0.0.md): TiDB Operator 2.0.0 is released. The v2 version introduces major refactoring from v1, with key changes including splitting the `TidbCluster` CRD into multiple CRDs, removing the dependency on StatefulSet, and introducing the Overlay feature for more flexible custom configurations. - [2.0.0-beta.0](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-2.0.0-beta.0.md): TiDB Operator 2.0.0-beta.0 is released. The v2 version introduces major refactoring from v1, with key changes including splitting the `TidbCluster` CRD into multiple CRDs, removing the dependency on StatefulSet, and introducing the Overlay feature for more flexible custom configurations. - v1.6 - [1.6.5](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.6.5.md): Learn about new features, improvements, and bug fixes in TiDB Operator 1.6.5. - [1.6.4](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.6.4.md): Learn about new features in TiDB Operator 1.6.4. - [1.6.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.6.3.md): Learn about bug fixes in TiDB Operator 1.6.3. - [1.6.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.6.2.md): Learn about new features, improvements, and bug fixes in TiDB Operator 1.6.2. - [1.6.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.6.1.md): Learn about new features, improvements, and bug fixes in TiDB Operator 1.6.1. - [1.6 GA](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.6.0.md): Learn about new features, improvements, and bug fixes in TiDB Operator 1.6.0. - [1.6.0-beta.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.6.0-beta.1.md): Learn about new features, improvements, and bug fixes in TiDB Operator 1.6.0-beta.1. - v1.5 - [1.5.5](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.5.5.md): Learn about new features and improvements in TiDB Operator 1.5.5. - [1.5.4](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.5.4.md): Learn about improvements and bug fixes in TiDB Operator 1.5.4. - [1.5.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.5.3.md): Learn about new features and bug fixes in TiDB Operator 1.5.3. - [1.5.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.5.2.md): TiDB Operator 1.5.2 released on January 19, 2024. New features include support for backing up and restoring data of a TiDB cluster across multiple AWS Kubernetes clusters to AWS storage using EBS volume snapshots. Improvements include better support for scenarios such as Stale Read and explicitly specifying PD addresses. Bug fixes address issues with changing meta information and PD member labels. - [1.5.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.5.1.md): TiDB Operator 1.5.1 was released on October 20, 2023. The new feature includes support for replacing volumes for PD, TiKV, and TiDB. Bug fixes include resolving errors from PVC modifier during manual TiKV eviction, fixing deadlock issues caused by TiKV eviction during volume replacement, addressing TidbCluster rollback during the upgrade process, and resolving the issue with the `MaxReservedTime` option for scheduled backup. - [1.5 GA](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.5.0.md): Learn about new features, improvements, and bug fixes in TiDB Operator 1.5.0. - [1.5.0-beta.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.5.0-beta.1.md): TiDB Operator 1.5.0-beta.1 was released on April 11, 2023. The new features include support for graceful restart of PD and TiDB Pods, managing TiCDC and TiProxy with Advanced StatefulSet, and defining a strategy to restart failed backup jobs. Improvements include upgrading Kubernetes dependencies, adding metrics for observability, and customizing Prometheus scraping settings. Bug fixes address the issue of unreachable pprof endpoint due to route conflicts with the metrics endpoint. - v1.4 - [1.4.7](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.7.md): TiDB Operator 1.4.7 was released on July 26, 2023. This version includes bug fixes, such as making `logBackupTemplate` optional in BackupSchedule CR. - [1.4.6](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.6.md): TiDB Operator 1.4.6 was released on July 19, 2023. The improvements include enabling volume resizing by default. Bug fixes address issues with executing backup and restore with BR >=v6.6.0 and the graceful drain for TiCDC when a non-SemVer image tag is used. - [1.4.5](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.5.md): TiDB Operator 1.4.5 was released on June 26, 2023. The improvements include adding metrics for TidbCluster reconcile errors, reconciler and worker queue observability, introducing `startUpScriptVersion` field for DM master, and support for rolling restart and scaling-in of TiCDC clusters. Bug fixes include suppressing GC for newly created scheduled backups, making `backupTemplate` optional in backup CR, and fixing issues related to Kubernetes cluster-level permission and `AdditionalVolumeMounts` for TidbCluster. - [1.4.4](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.4.md): TiDB Operator 1.4.4 released on March 13, 2023. New features include support for volume-snapshot backup and restore on TiDB cluster with TiFlash, accurate backup size display, retries for snapshot backups, and integrated management of log and snapshot backups. Bug fixes address sync failure with custom TiDB builds, volume-snapshot backup data restoration, panic during snapshot backup, and potential failure during restore. - [1.4.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.3.md): TiDB Operator version 1.4.3 was released on February 24, 2023. Bug fixes include resolving the TiFlash metric server not listening on correct IPv6 addresses when the `preferIPv6` configuration is enabled, and fixing the issue of TiDB Operator continuously modifying EBS disks in AWS when the feature gate `VolumeModifying` is enabled and EBS parameters are missing in `StorageClass`. - [1.4.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.2.md): TiDB Operator 1.4.2 was released on February 3, 2023. This version fixed the issue where TiFlash does not listen on IPv6 addresses when the `preferIPv6` configuration is enabled. - [1.4.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.1.md): TiDB Operator 1.4.1 was released on January 13, 2023. New features include support for cleaning up failed instances of PD, TiKV, and TiFlash components. Improvements include support for configuring QPS and Burst for the Kubernetes client. Bug fixes address the issue of TiDB Controller Manager panicking without PV permission. - [1.4 GA](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.0.md): TiDB Operator 1.4.0 was released on December 29, 2022. New features include support for managing TiDB Dashboard in a separate CRD, configuring Readiness Probe for TiKV and PD, and backup and restore based on Amazon EBS volume-snapshot. Bug fixes address issues with backup based on EBS snapshot and log backup stopping in the Complete state. - [1.4.0-beta.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.0-beta.3.md): TiDB Operator 1.4.0-beta.3 was released on December 2, 2022. The new features include experimental support for TiProxy and GA for snapshot backup and restore based on Amazon EBS. The release also includes bug fixes for error messages, volume-snapshot backup cleanup failure, and backup failure with massive TiKV nodes. - [1.4.0-beta.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.0-beta.2.md): TiDB Operator 1.4.0-beta.2 was released on November 11, 2022. Bug fixes include an issue with `BackupSchedule` not setting a prefix when using Azure Blob Storage and an upgrade of AWS SDK to v1.44.72 to support the Asia Pacific (Jakarta) region. - [1.4.0-beta.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.0-beta.1.md): TiDB Operator 1.4.0-beta.1 was released on October 27, 2022. The new feature includes support for snapshot backup and restore based on Amazon EBS, with benefits such as reducing the impact of backup on QPS to less than 5% and shortening the backup and restore time. Bug fixes include updating the log backup checkpoint ts after TiDB Operator restarts and when TLS is enabled for the TiDB cluster. - [1.4.0-alpha.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.4.0-alpha.1.md): TiDB Operator 1.4.0-alpha.1 was released on September 26, 2022. Changes include disabling volume modification by default, rolling update changes for TiCDC, and new features such as setting location labels for tidb-server and scaling multiple TiFlash and TiKV Pods simultaneously. Improvements include optimizing prometheus remoteWrite configuration for TidbMonitor and adding metrics port for TiFlash Service. Bug fixes address issues with cluster sync getting stuck and TiDB Operator panicking if PD spec is nil. - v1.3 - [1.3.10](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.10.md): TiDB Operator 1.3.10 was released on February 24, 2023. The new version includes an improvement to bump the Go version to 1.19 in order to fix security vulnerabilities. - [1.3.9](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.9.md): TiDB Operator 1.3.9 was released on October 10, 2022. This version includes a bug fix for the issue that PD upgrade would get stuck if the `acrossK8s` field is set but the `clusterDomain` field is not set. - [1.3.8](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.8.md): TiDB Operator 1.3.8 was released on September 13, 2022. The new feature includes special annotations for TidbCluster to configure the minimum ready duration for TiDB, TiKV, and TiFlash. The minimum ready duration specifies the minimum number of seconds that a newly created Pod takes to be ready during a rolling upgrade. An improvement is the support for graceful upgrade of a TiCDC Pod if the Pod version is v6.3.0 or later versions. - [1.3.7](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.7.md): TiDB Operator 1.3.7 was released on August 1, 2022. The new features include the addition of the `suspendAction` field to suspend any component. Improvements include recreating the `StatefulSet` of a component after PVCs are scaled up and continuing scale-up if a leader eviction times out. Bug fixes address issues with TiKV upgrades when using local storage and potential backup file leaks after cleanup. - [1.3.6](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.6.md): TiDB Operator 1.3.6 was released on July 5, 2022. The improvement in this version includes reducing the impact of PVC scale-up on cluster performance by scaling up PVCs pod by pod and evicting TiKV leader before resizing PVCs of TiKV. - [1.3.5](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.5.md): TiDB Operator 1.3.5 was released on June 29, 2022. The new feature includes support for backing up and restoring data from Azure Blob Storage. - [1.3.4](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.4.md): TiDB Operator 1.3.4 was released on June 22, 2022. The improvement in this version includes adding the 'volumes' field in the status information of each component to display the volume status. - [1.3.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.3.md): TiDB Operator 1.3.3 was released on May 17, 2022. The new feature includes adding a new field to customize the tidb service port. Several bug fixes were made, including fixing issues with leader scheduler leakage, incompatibility with ARM architecture, panic when tidb Service has no Endpoints, and loss of Labels and Annotations after TiDB Operator fails to access the Kubernetes server. - [1.3.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.2.md): TiDB Operator 1.3.2 was released on March 18, 2022. The improvements include support for TiDB to run on Istio-enabled Kubernetes clusters and support for multi-arch docker image. - [1.3.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.1.md): TiDB Operator version 1.3.1 was released on February 24, 2022. The release includes compatibility changes, new features, improvements, and bug fixes. Users must upgrade TiDB Operator to avoid TiFlash losing metadata. A new field `spec.dnsPolicy` was added to support configuring `DNSPolicy` for Pods. The `tidb-lightning` Helm chart now uses `local` backend as the default backend. Bug fixes include issues with TiFlash losing metadata and not working if certain fields are not set in TiFlash's config, as well as TiDB cluster's PD components failing to start due to discovery service errors. - [1.3 GA](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.0.md): TiDB Operator 1.3.0 has compatibility changes, new features, improvements, and bug fixes. Upgrading to v1.3.0 directly may cause failed rolling upgrade if a TiDB cluster is deployed across multiple Kubernetes clusters. It is recommended to upgrade TiDB Operator to v1.3.1 before upgrading TiFlash. New features include configuring DNS for Pods, setting random passwords for TiDB, and supporting one-time recover for TiKV/TiFlash/DM Worker. Improvements include pre-checking VolumeMount existence and enhancing the feature of deploying a TiDB cluster across Kubernetes clusters. Bug fixes include fixing the issue that tidb scheduler cannot be deployed on Kubernetes v1.23 or later versions. - [1.3.0-beta.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.3.0-beta.1.md): TiDB Operator 1.3.0-beta.1 was released on January 12, 2022. The release includes compatibility changes, rolling update changes, new features, and improvements. Some changes may impact TiDB cluster management, such as the deletion of ValidatingWebhook and MutatingWebhook, and the need to upgrade TiDB Operator before deploying TiFlash. New features include support for configuring resource usage for the init container of TiFlash and enabling continuous profiling for the TiDB cluster. Improvements include optimizing the user experience of heterogeneous clusters and updating Grafana images for enhanced security. - v1.2 - [1.2.7](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.7.md): TiDB Operator 1.2.7 was released on February 17, 2022. The new feature includes the addition of a new field `spec.pd.startUpScriptVersion` to use the `dig` command instead of `nslookup` to lookup domain in the startup script of PD. An improvement was made to pre-check whether `VolumeMount` exists when the StatefulSet of components is deployed or updated to avoid failed rolling upgrade. - [1.2.6](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.6.md): TiDB Operator 1.2.6 was released on January 4, 2022. The improvements include refining the retry logic when updating the status of the Backup and Restore CR. - [1.2.5](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.5.md): TiDB Operator 1.2.5 was released on December 27, 2021. The release includes improvements such as support for configuring all fields in `ComponentSpec` for DM, init container `resources` for TiFlash, and the `ssl-ca` parameter for TiDB. Bug fixes include issues with component roll update, TidbCluster spec update, goroutine leak, and high-level security issues. - [1.2.4](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.4.md): TiDB Operator 1.2.4 was released on October 21, 2021. The update includes changes to the rolling update process, new features such as customizing prometheus rules and reloading configurations, improvements to the TiFlash rolling upgrade process and support for deleting backup data in batches. Bug fixes were also made to address security vulnerabilities in the images and to resolve issues with retaining backup data when the Backup job is running. - [1.2.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.3.md): TiDB Operator 1.2.3 was released on September 7, 2021. This version fixed the TiFlash Pod rolling recreation issue that occurred after upgrading to v1.2.2. - [1.2.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.2.md): TiDB Operator 1.2.2 was released on September 3, 2021. Upgrading the operator will recreate the TiDBMonitor and TiFlash Pods. The new feature includes support for dynamically reloading configurations in TiDBMonitor. Bug fixes address upgrade failures of TiCDC from an earlier version to v5.2.0. - [1.2.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.1.md): TiDB Operator 1.2.1 was released on August 18, 2021. The update includes changes to the rolling update process, which may cause the recreation of the TiCDC Pod if `hostNetwork` is enabled. Additionally, improvements have been made to support configuring `hostNetwork` for all components in TidbCluster, allowing all components to use the host network. - [1.2 GA](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.0.md): TiDB Operator 1.2.0 was released on July 29, 2021. The update includes changes to the rolling update process, new features such as setting Prometheus retentionTime and priorityClassName, improvements to the default Region leader eviction timeout, and bug fixes related to URL parsing in TiDBMonitor. - [1.2.0-rc.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.0-rc.2.md): TiDB Operator 1.2.0-rc.2 was released on July 2, 2021. The new features include support for passing raw TOML config for TiCDC, setting StorageVolumes, AdditionalVolumes, and AdditionalVolumeMounts for TiCDC, and modifying Grafana dashboard. Improvements include using the TiKV version as the tag for BR toolImage, handling PVC during scaling of TiDB, and adding liveness and readiness probes for TiDB Operator. Bug fixes address issues with the deployment of heterogeneous clusters and the continuous update of TiDB service and TidbCluster status. - [1.2.0-rc.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.0-rc.1.md): TiDB Operator 1.2.0-rc.1 was released on May 28, 2021. The update includes changes to the Pump Pod, support for customized labels for TidbCluster Pods and services, full lifecycle management for Pump, and various improvements and bug fixes. Notable improvements include masking the backup password in logging, additional volumeMounts field for Grafana, and additional printout columns for TidbMonitor. Bug fixes address issues with TidbMonitor, PD member count, DM-master restart, rolling update, and backup using Dumpling. - [1.2.0-beta.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.0-beta.2.md): TiDB Operator 1.2.0-beta.2 was released on April 29, 2021. Upgrading the operator will recreate TidbMonitor and DM-master Pods. New features include support for monitoring multiple TidbClusters with TLS enabled, configuring podSecurityContext and topologySpreadConstraints for all TiDB components, deploying a DmCluster in a different namespace, and installing TiDB Operator with only namespace-scoped permissions. Improvements include adding a readiness probe for the TidbMonitor Pod, optimizing TidbMonitor for DmCluster with TLS enabled, and supporting not generating Prometheus alert rules. Bug fixes address issues with TiDB instances in TiDB Dashboard after scaling in and useless sync of TidbCluster CR caused by the update of `lastHeartbeatTime` in `status.tikv.stores`. - [1.2.0-beta.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.0-beta.1.md): TiDB Operator 1.2.0-beta.1 was released on April 7, 2021. The new version includes compatibility changes, rolling update changes, new features, improvements, and bug fixes. Some notable new features include support for setting customized environment variables for backup and restore job containers, additional volume and volumeMount configurations to TidbMonitor, and support for configuring durations for leader election. The release also includes various improvements and bug fixes to enhance the performance and stability of the TiDB Operator. - [1.2.0-alpha.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.2.0-alpha.1.md): TiDB Operator 1.2.0-alpha.1 was released on January 15, 2021. The update includes the ability to deploy one TiDB cluster across multiple Kubernetes clusters, support for DM 2.0, auto-scaling with PD API, and canary upgrade of TiDB Operator. Improvements include local backend support for the TiDB Lightning chart, TLS support for the TiDB Lightning chart and TiKV Importer chart, persisting checkpoint for TiDB Lightning helm chart, support for Thanos sidecar for monitoring multiple clusters, and migration from Deployment to StatefulSet for TidbMonitor. Other notable changes include optimized rate limiter intervals and changes in the directory to save customized alert rules in TidbMonitor. - v1.1 - [1.1.15](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.15.md): TiDB Operator 1.1.15 was released on February 17, 2022. This version includes a bug fix for a potential goroutine leak when TiDB Operator checks the Region leader count of TiKV. - [1.1.14](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.14.md): TiDB Operator 1.1.14 was released on October 21, 2021. This version includes bug fixes for security vulnerabilities in the `tidb-backup-manager` and `tidb-operator` images. - [1.1.13](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.13.md): TiDB Operator 1.1.13 was released on July 2, 2021. The release includes improvements such as support for configuring TLS certificates for TiCDC sinks, using TiKV version as the tag for BR `toolImage` if no tag is specified, handling PVC during scaling of TiDB, and masking the backup password in logging. Bug fixes include resolving issues with TiDB Operator panicking during the deployment of heterogeneous clusters and instances being kept in TiDB Dashboard after being scaled in. - [1.1.12](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.12.md): TiDB Operator 1.1.12 was released on April 15, 2021. New features include support for customized environment variables for backup and restore job containers, additional volume and volumeMount configurations for TidbMonitor, and the use of new service account resources in the tidb-operator chart. Improvements include DNS lookup failure exception retry, support for multiple PVCs for PD during scaling and failover, and optimization of the PodsAreChanged function. Bug fixes address issues with PVC size configuration, panic issue with TLS enabled TidbCluster CR, and wrong PVC status in UnjoinedMembers for PD and DM. - [1.1.11](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.11.md): TiDB Operator 1.1.11 was released on February 26, 2021. New features include support for configuring leader election durations and setting customized store labels. Improvements include TiFlash rolling upgrade logic, retrieving region leader count from TiKV Pod directly, and printing RocksDB and Raft logs to stdout for Grafana support. - [1.1.10](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.10.md): TiDB Operator 1.1.10 was released on January 28, 2021. The new version includes compatibility changes, rolling update changes, new features, improvements, and bug fixes. Some notable changes include the support for canary upgrade, `remotewrite` configuration for TidbMonitor, and customizing storage config for TiDB slow log. The update also fixes issues related to TLS-enabled backup and restore jobs, advanced StatefulSet, and recovery of TiKV component. - [1.1.9](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.9.md): TiDB Operator 1.1.9 was released on December 28, 2020. The new version includes support for defining the image used for Backup and Restore operations, as well as bug fixes for issues with Prometheus metrics and compatibility with GCS for backup and restore operations. - [1.1.8](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.8.md): TiDB Operator 1.1.8 was released on December 21, 2020. New features include support for arbitrary Volume and VolumeMount for various components, enabling the use of NFS or other Kubernetes supported volume sources for backup/restore workflow. Improvements include support for cluster and client TLS, setting additional ports for TiDB service, and Prometheus to scrape metrics data from multiple TiDB clusters. Bug fixes address issues such as TiDB cluster deployment failure, non-ASCII character password error, misrecognition of TiFlash Pods, and crashing of tidb-controller-manager Pod. - [1.1.7](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.7.md): TiDB Operator 1.1.7 was released on November 13, 2020. The new version includes compatibility changes, new features, improvements, and bug fixes. Some notable changes include the support for specifying the tool image for backup and restore, support for mounting multiple PVs for TiDB, TiKV, and PD, and the ability to support HA scheduling when failover happens. Additionally, the release includes improvements such as forbidding the scaling in of TiKV when the number of UP stores is equal to or less than 3, and bug fixes including fixing the issue that PD cannot scale into zero if there are other PD members outside of the TidbCluster. - [1.1.6](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.6.md): TiDB Operator 1.1.6 was released on October 16, 2020. Compatibility changes include migration of `spec.pd.config` from YAML to TOML format, with some parameters requiring manual editing. New features include customizing arguments for BR, configurable TiKV evict leader timeout, and monitoring multiple TiDB clusters with one TidbMonitor CR. Improvements involve support for passing raw TOML config for various components and bug fixes address the problem of bootstrapping multiple PD clusters. - [1.1.5](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.5.md): TiDB Operator 1.1.5 was released on September 18, 2020. The new version includes compatibility changes, new features, improvements, and bug fixes. Some notable changes include support for configuring serviceAccount for TiDB/Pump/PD, labels configuration for TiDB, and recovery from failover for TiFlash and TiKV. Additionally, there are improvements in adapting configurations to v4.0.6, scaling taking precedence over upgrading, and bug fixes for the Grafana container in the TidbMonitor CR. - [1.1.4](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.4.md): TiDB Operator 1.1.4 was released on August 21, 2020. Notable changes include the addition of TableFilter to BackupSpec and RestoreSpec, support for customizing environment variables for the initializer container, patching PVCs when storage request is increased, TLS support for Backup & Restore with Dumpling & TiDB Lightning, and support for max-index-length TiDB config option. Other changes include fixes for goroutine and memory leaks, support for TLS for TiFlash, and configuration of TZ environment for admission webhook and advanced statefulset controller. - [1.1.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.3.md): TiDB Operator 1.1.3 was released on July 27, 2020. Action required includes adding a field `cleanPolicy` in `BackupSpec` and replacing `mydumper` with `dumpling` for backup. Other notable changes include updating tools in backup manager, adding TLS support for TiCDC, and support for auto-scaling by storage for TiKV in `TidbClusterAutoScaler`. Various bug fixes and updates were also made. - [1.1.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.2.md): TiDB Operator version 1.1.2 has been released on July 1, 2020. An issue with PD 4.0.2 has been fixed, requiring an upgrade before deploying TiDB 4.0.2 and later versions. Other changes include collecting metrics for TiCDC, TiDB Lightning, and TiKV Importer, updating PD/TiDB/TiKV config to v4.0.2, fixing a bug with `PD` Member, supporting Auto-Scaler Reference in `TidbCluster` Status, and configuring container lifecycle hooks and `terminationGracePeriodSeconds` in TiDB spec. - [1.1.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.1.md): TiDB Operator version 1.1.1 was released on June 19, 2020. Notable changes include support for adding sidecars to TiDB, TiKV, PD, etc. A cross check was added to ensure TiKV is not scaled or upgraded at the same time. Bugs related to TidbMonitor, alert rules, and pod scaling were fixed. Updates were made to TiDB Operator examples and configurations. Additional features include enabling direct visit to PD Dashboard, specifying subdirectory within the data volume, and support for LoadBalancerSourceRanges in ServiceSpec. The DM version was bumped to v2.0.0-beta.1, and support for scraping Pump and Drainer metrics in TidbMonitor was added. - [1.1 GA](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1-ga.md): Upgrade from v1.0.x, breaking changes, and other notable changes. Notable changes include support for preemption in tidb-scheduler, update BR to v4.0.0-rc.2, and support TiCDC in TidbCluster. The release also includes improvements in performance and updates to TiDB/TiKV/PD configuration to 4.0.0 GA version. - [1.1.0-rc.4](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.0-rc.4.md): TiDB Operator 1.1 RC.4 was released on May 15, 2020. The new version supports separate TiDB client certificates for each component and allows customization of backup path prefix for remote storage. It also fixes bugs related to service annotations and reconciling TiDB service. Other notable changes include support for TiCDC in TidbCluster CR, creating node pools for TiFlash and CDC on ACK and EKS, and backup and restore with GCS using BR. Additionally, it updates TiDBConfig and TiKVConfig to support the 4.0.0-rc version and adds external strategy ability for TidbClusterAutoScaler. PVReclaimPolicy for TidbMonitor when storage is enabled is also exposed. - [1.1.0-rc.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.0-rc.3.md): TiDB Operator 1.1 RC.3 was released on April 30, 2020. Notable changes include support for TiFlash metrics in TidbMonitor, fixing bugs related to failover pods and statefulsets, and adding new features like configuring Ingress in TidbMonitor and supporting failover for TiFlash. Other changes include updates to terraform scripts and adding new fields in TiKVConfig. - [1.1.0-rc.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.0-rc.2.md): TiDB Operator 1.1 RC.2 was released on April 15, 2020. Action required includes changing TiDB pod readiness probe and setting spec.paused to true before upgrading. Notable changes include adding status field for TidbAutoScaler CR, emitting more events for TidbCluster and TidbClusterAutoScaler, and adding TLS support for TiKV metrics API. Other changes involve adding a switch to skip PD Dashboard TLS configuration, supporting TiFlash in TidbCluster CR, and fixing errors related to alertmanager in TidbMonitor. - [1.1.0-rc.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.0-rc.1.md): The new release includes action required changes such as configuring `--advertise-address` for `tidb-server` and adding `tlsClient.tlsSecret` field in the backup and restore spec. Other notable changes include using `tidb-lightning` in `Restore`, adding `cert-allowed-cn` support to TiDB components, and fixing PD `location-labels` configuration. Additionally, there are several fixes and updates for TiDB clusters, including support for deploying clusters with TidbCluster and TidbMonitor CRs via Terraform. TLS support has been added for Pump, Drainer, and MySQL clients, and various bug fixes and improvements have been made. - [1.1.0-beta.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.0-beta.2.md): TiDB Operator 1.1 Beta.2 has been released on February 26, 2020. The default storage class now defaults to Kubernetes default storage class. Users need to set default storage class explicitly in their TiDB cluster helm or YAML files if different than Kubernetes default. Other changes include the ability to configure affinity and tolerations for Backup and Restore, support for TidbCluster Auto-scaling based on CPU average utilization load, and more. Additionally, several bug fixes and improvements have been made. - [1.1.0-beta.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.1.0-beta.1.md): The new version requires action to add timezone support for all charts. Other notable changes include support for backup to S3, scaling in/out with deleted slots feature, and managing Pump cluster. Additional changes involve refining configuration schema, setting default name of instance label key, and upgrading default backup image. The release also includes fixes and improvements for various components. - v1.0 - [1.0.7](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.7.md): TiDB Operator 1.0.7 was released on June 16, 2020. Notable changes include fixing alert rules lost after rolling upgrade, upgrading local volume provisioner to 2.3.4, fixing operator failover config invalid, removing unnecessary duplicated docs, updating doc links and image in readme, emitting events when PD failover, fixing some broken urls, and removing some not very useful update events. - [1.0.6](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.6.md): TiDB Operator 1.0.6 was released on December 27, 2019. Users need to migrate configs from the old `values.yaml` to the new one to avoid monitor pod failures. The new release includes improvements in monitor, TiDB Scheduler, compatibility, TiKV Importer, E2E, and CI. Notable changes include enabling alert rule persistence, adding node & pod info in TiDB Grafana, refining scheduler error messages, fixing compatibility issues in Kubernetes v1.17, and adjusting the release CI script. - [1.0.5](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.5.md): TiDB Operator version 1.0.5 was released on December 11, 2019. The new features include fixing backup failure issue, recommending deployment of TiDB and Pump on the same node, fixing RBAC permission in Kubernetes v1.16, and fixing e2e nil point dereference. No action is required for upgrading from v1.0.4. - [1.0.4](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.4.md): TiDB Operator version 1.0.4 was released on November 23, 2019. The new features include HostNetwork support, podSecurityContext support, and new Helm charts for TiDB Lightning and TiDB Binlog. There are also bug fixes and changes, and a recommendation to upgrade to v1.0.4 from v1.1.0.alpha. - [1.0.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.3.md): TiDB Operator 1.0.3 was released on November 13, 2019. The new version requires an upgrade to TiDB v3.0.5 and adds timezone support for all charts. Existing TiDB clusters with customized timezones will trigger a rolling update. Improvements include timezone support and configuring resource requests and limits for all containers of the TiDB cluster. Bug fixes include upgrading default TiDB version to v3.0.5 and adding timezone support for all containers of the TiDB cluster. - [1.0.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.2.md): TiDB Operator version 1.0.2 has made several improvements and bug fixes. The AWS Terraform script now suspends the replacing behavior for TiKV auto-scaling-group to prevent data loss. It also adds a new VM manager, sets default externalTrafficPolicy to be Local for TiDB service, and fixes various compatibility issues. The release also includes bug fixes for tkctl version, Terraform script, statefulsets apiVersion, TiDB Loadbalancer, and more. Overall, the release aims to enhance stability and compatibility for TiDB Operator on AWS, GCP, and Aliyun. - [1.0.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.1.md): TiDB Operator version 1.0.1 was released on September 17, 2019. The release includes important bug fixes and improvements. Users of version 1.0.0 or prior must upgrade to avoid serious bugs that could cause service outage. The release also includes modularization of GCP Terraform, support for expanding cloud storage PV dynamically, and improvements to backup tool image. Additionally, several bug fixes were made to address issues such as TiKV scale-in failure and orphaned pods cleaner bugs. - [1.0 GA](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0-ga.md): TiDB Operator 1.0.0 has been released on July 30, 2019. The new version requires action to be taken for configuration changes in `values.yaml`. The release includes stability test cases, improvements in GKE SSD setup, AWS Terraform scripts, and bug fixes for sysbench installation and TiKV metrics monitoring. Detailed bug fixes and changes include upgrading TiDB monitor, specifying TiKV status address, and enabling nlb cross zone load balancing by default. Multiple TiDB clusters management is now supported in Alibaba Cloud. The release also includes changes in configuration for TiDB, TiKV, and PD in charts, and an increase in default storage size for Pump. - [1.0.0-rc.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.0-rc.1.md): TiDB Operator 1.0 RC.1 was released on July 12, 2019. The new version includes stability test cases, improvements such as increasing TiKV GC life time, and bug fixes like fixing unbound variables in the backup script and scheduled backup bugs. It also supports force upgrade when PD cluster is unavailable and adds Amazon S3 support for backup/restore features. The release notes also detail various bug fixes and changes made in the new version. - [1.0.0-beta.3](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.0-beta.3.md): TiDB Operator 1.0 Beta.3 was released on June 6, 2019. The new version includes the removal of `nodeSelectorRequired` from values.yaml and the addition of stability cases, new features, documentation improvements, and bug fixes. Some notable new features include ConfigMap rollout management, stable scheduling for pods, and support for adding additional pod annotations. The default TiDB version has been upgraded to v3.0.0-rc.1, and various bug fixes and changes have been implemented. Overall, the release focuses on stability, new features, and documentation improvements. - [1.0.0-beta.2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.0-beta.2.md): TiDB Operator 1.0 Beta.2 has been released on May 10, 2019. The new version includes enhanced stability, improved ease of use, bug fixes, and other improvements. Some of the key changes include refactored e2e test, one-command deployment for AWS and Aliyun, and support for slow log of TiDB. Numerous bug fixes and detailed changes have also been made to improve the overall performance and user experience. - [1.0.0-beta.1-p2](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.0-beta.1-p2.md): TiDB Operator 1.0 Beta.1 P2 was released on February 21, 2019. Notable changes include a new algorithm for scheduler HA predicate, addition of TiDB discovery service, serial scheduling, change in tolerations type to an array, direct start when there is a join file, addition of code coverage icon, omission of just the empty leaves in `values.yml`, backup to ceph object storage in charts, and addition of `ClusterIDLabelKey` label to TidbCluster. - [1.0.0-beta.1-p1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.0-beta.1-p1.md): TiDB Operator 1.0 Beta.1 P1 was released on January 7, 2019. The bug fixes include resolving scheduler policy issues for Kubernetes v1.10, v1.11, and v1.12. The documentation updates propose adding multiple statefulsets support to TiDB Operator and updating the roadmap. - [1.0.0-beta.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.0-beta.1.md): TiDB Operator 1.0 Beta.1 was released on December 27, 2018. The release includes bug fixes such as pd_control bug, orphan pod cleaner, scheduler configuration fix, Grafana configuration fix, and more. Minor improvements include adding Kubernetes 1.12 local DinD scripts, bumping default TiDB to v2.1.0, releasing tidb-operator/tidb-cluster charts, and more. - [1.0.0-beta.0](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-1.0.0-beta.0.md): TiDB Operator 1.0 Beta.0 was released on November 26, 2018. Notable changes include the introduction of basic chaos testing, improved unit test coverage, default log-level values for PD/TiKV/TiDB, and various bug fixes and enhancements. The release also includes a user guide and migration to Go 1.11 module. - v0 - [0.4.0](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-0.4.0.md): TiDB Operator 0.4.0 was released on November 9, 2018. Notable changes include extending Kubernetes scheduler for TiDB data awareness, restoring backup data from GCS bucket, and setting password for TiDB when first deployed. Minor changes and bug fixes include updating roadmap, adding unit tests, E2E tests, adding TiDB failover limit, synchronizing PV reclaim policy early, using helm release name as instance label, and fixing local PV setup script. - [0.3.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-0.3.1.md): TiDB Operator 0.3.1 was released on October 31, 2018. Minor changes include parameterizing the serviceAccount, bumping TiDB to v2.0.7, and allowing user-specified config files. Bug fixes address issues such as parallel upgrade bugs and recovery after a failed upgrade. - [0.3.0](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-0.3.0.md): TiDB Operator 0.3.0 was released on October 12, 2018. Notable changes include the addition of full backup support, TiDB Binlog support, graceful upgrade feature, and the ability to persist monitor data. - [0.2.1](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-0.2.1.md): TiDB Operator 0.2.1 was released on September 20, 2018. This version includes bug fixes for retry on conflict logic, TiDB timezone configuration, failover, and repeated updating of pod and pd/tidb StatefulSet. - [0.2.0](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-0.2.0.md): TiDB Operator 0.2.0 was released on September 11, 2018. Notable changes include experimental support for auto-failover, unification of Tiller and TiDB Operator managed resources labels, managing TiDB service via Tiller, adding toleration for TiDB cluster components, and refactoring upgrade functions as interface. Additionally, a script to set up DinD environment easily was added, and code was linted and formatted in CI. - [0.1.0](https://docs.pingcap.com/tidb-in-kubernetes/dev/release-0.1.0.md): TiDB Operator 0.1.0 was released on August 22, 2018. Notable changes include the ability to bootstrap multiple TiDB clusters, support for monitoring deployment and Helm charts, basic Network PV/Local PV support, safe scaling of the TiDB cluster, orderly cluster upgrades, and stopping the TiDB process without terminating the Pod. Additionally, cluster meta info can be synchronized to POD/PV/PVC labels, and basic unit tests & E2E tests are available. Tutorials for GKE and local DinD are also provided.