TiDB Operator 1.6.1 Release Notes

Release date: December 25, 2024

TiDB Operator version: 1.6.1

New features

Support authentication for backup and restore operations using Azure Blob Storage Shared Access Signature (SAS) tokens (#5720, @tennix)
The VolumeReplace feature supports the TiFlash component (#5685, @rajsuvariya)
Add a more straightforward interface for Log Backup that supports pausing and resuming backup tasks (#5710, @RidRisR)
Support deleting Log Backup tasks by removing their associated Backup custom resource (CR) (#5754, @RidRisR)
The VolumeModify feature supports modifying Azure Premium SSD v2 disks. To use this feature, you need to grant the tidb-controller-manager permission to operate Azure disk through a node or Pod. (#5958, @handlerww)

The VolumeModify feature no longer performs leader eviction for TiKV, reducing modification time (#5826, @csuzhangxc)
Support specifying the minimum wait time during PD Pod rolling updates by using annotations (#5827, @csuzhangxc)
The VolumeReplace feature supports customizing the number of spare replicas for PD and TiKV (#5666, @anish-db)
The VolumeReplace feature can be enabled for specific TiDB clusters (#5670, @rajsuvariya)
Optimize the primary transfer logic of the PD microservice to reduce the number of primary transfer operations during component updates (#5643, @HuSharp)
Support setting LoadBalancerClass for the TiDB service (#5964, @csuzhangxc)

Fix the issue that EBS snapshot restore incorrectly succeeds when no TiKV instances are configured or TiKV replica is set to 0 (#5659, @BornChanger)
Fix the issue that ClusterRole and ClusterRoleBinding resources are not properly cleaned up when you delete a TidbMonitor that monitors multiple TiDB clusters across namespaces (#5956, @csuzhangxc)
Fix a type mismatch issue in the .spec.prometheus.remoteWrite.remoteTimeout field of TidbMonitor (#5734, @IMMORTALxJO)