TiDB Operator 1.1.10 Release Notes

• Upgrading TiDB Operator will cause the recreation of the TidbMonitor Pod due to #3684

• Support canary upgrade of TiDB Operator (, @shonge, , @cvvz)
• TidbMonitor supports configuration (, @mikechengwei)
• Support configuring init containers for components in the TiDB cluster (, @handlerww)
• Add local backend support to the TiDB Lightning chart (, @csuzhangxc)

• Add the tidb_cluster label for the scrape jobs in TidbMonitor to support monitoring multiple clusters (, @mikechengwei)
• Supports persisting checkpoint for the TiDB Lightning helm chart (, @csuzhangxc)
• Change the directory of the customized alert rules in TidbMonitor from tidb:${tidb_image_version} to tidb:${initializer_image_version} so that when the TiDB cluster is upgraded afterwards, the TidbMonitor Pod will not be recreated (, @BinChenn)

• Fix the issue that when TLS is enabled for the TiDB cluster, if spec.from or is not configured, backup and restore jobs with BR might fail (, @BinChenn)
• Fix the bug that if the advanced StatefulSet is enabled and delete-slots annotations are added for PD or TiKV, the Pods whose ordinal is bigger than replicas - 1 will be terminated directly without any pre-delete operations such as evicting leaders (, @cvvz)
• Fix the issue that when the TiKV cluster is not bootstrapped due to incorrect configuration, the TiKV component could not be recovered by editing TidbCluster CR (, @cvvz)