From fab9bd3be0005791138cc20db133f1d8b9999c71 Mon Sep 17 00:00:00 2001 From: csuzhangxc Date: Mon, 15 Jan 2024 07:38:03 +0000 Subject: [PATCH 1/6] en,zh: add v1.5.2 release notes --- en/TOC.md | 1 + en/releases/release-1.5.2.md | 24 ++++++++++++++++++++++++ zh/TOC.md | 1 + zh/releases/release-1.5.2.md | 22 ++++++++++++++++++++++ 4 files changed, 48 insertions(+) create mode 100644 en/releases/release-1.5.2.md create mode 100644 zh/releases/release-1.5.2.md diff --git a/en/TOC.md b/en/TOC.md index 9064917f1..63001fbfb 100644 --- a/en/TOC.md +++ b/en/TOC.md @@ -125,6 +125,7 @@ - [PingCAP Clinic Diagnostic Data](clinic-data-collection.md) - Release Notes - v1.5 + - [1.5.2](releases/release-1.5.2.md) - [1.5.1](releases/release-1.5.1.md) - [1.5 GA](releases/release-1.5.0.md) - [1.5.0-beta.1](releases/release-1.5.0-beta.1.md) diff --git a/en/releases/release-1.5.2.md b/en/releases/release-1.5.2.md new file mode 100644 index 000000000..9fce65368 --- /dev/null +++ b/en/releases/release-1.5.2.md @@ -0,0 +1,24 @@ +--- +title: TiDB Operator 1.5.2 Release Notes +--- + +# TiDB Operator 1.5.2 Release Notes + +Release date: January 19, 2023 + +TiDB Operator version: 1.5.2 + +## New features + +- Support replacing volumes for PD, TiKV, and TiDB ([#5150](https://github.com/pingcap/tidb-operator/pull/5150), [@anish-db](https://github.com/anish-db)) + +## Improvements + +- `startScriptVersion: v2` supports waiting for Pod IP to match the one published to external DNS before starting a PD or TiKV to better support scenarios such as Stale Read ([#5381](https://github.com/pingcap/tidb-operator/pull/5381), [@smineyev81](https://github.com/smineyev81)) +- `startScriptVersion: v2` supports explicitly specifying PD addresses to better support scenarios where TiDB clusters are deployed across Kubernetes ([#5400](https://github.com/pingcap/tidb-operator/pull/5400), [@smineyev81](https://github.com/smineyev81)) +- tidb-operator Helm Chart supports specify resource lock for leader election when deploying Advanced-StatefulSet ([#5448](https://github.com/pingcap/tidb-operator/pull/5448), [@csuzhangxc](https://github.com/csuzhangxc)) + +## Bug fixes + +- Fixed the issue that changing meta information such as annotations and replacing volume at the same time may cause a deadlock for TiDB Operator reconcile ([#5382](https://github.com/pingcap/tidb-operator/pull/5382), [@anish-db](https://github.com/anish-db)) +- Fixed the issue that the PD member might be set the wrong label when replacing volume ([#5393](https://github.com/pingcap/tidb-operator/pull/5393), [@anish-db](https://github.com/anish-db)) diff --git a/zh/TOC.md b/zh/TOC.md index 10e964f28..41d600c8c 100644 --- a/zh/TOC.md +++ b/zh/TOC.md @@ -125,6 +125,7 @@ - [PingCAP Clinic 数据采集范围说明](clinic-data-collection.md) - 版本发布历史 - v1.5 + - [1.5.2](releases/release-1.5.2.md) - [1.5.1](releases/release-1.5.1.md) - [1.5 GA](releases/release-1.5.0.md) - [1.5.0-beta.1](releases/release-1.5.0-beta.1.md) diff --git a/zh/releases/release-1.5.2.md b/zh/releases/release-1.5.2.md new file mode 100644 index 000000000..45b0725d8 --- /dev/null +++ b/zh/releases/release-1.5.2.md @@ -0,0 +1,22 @@ +--- +title: TiDB Operator 1.5.2 Release Notes +--- + +# TiDB Operator 1.5.2 Release Notes + +发布日期: 2024 年 1 月 19 日 + +TiDB Operator 版本：1.5.2 + +## 新功能 + +## 优化提升 + +- `startScriptVersion: v2` 支持在重启 PD、TiKV 时等待 Pod IP 与 DNS 解析一致后再进行启动以更好地支持 Stale Read 等场景 ([#5381](https://github.com/pingcap/tidb-operator/pull/5381), [@smineyev81](https://github.com/smineyev81)) +- `startScriptVersion: v2` 支持显式指定 PD 地址以更好地支持跨 Kubernetes 部署 TiDB 集群的场景 ([#5400](https://github.com/pingcap/tidb-operator/pull/5400), [@smineyev81](https://github.com/smineyev81)) +- tidb-operator Helm Chart 支持在部署 Advanced-StatefulSet 时指定 leader election 的 resource lock ([#5448](https://github.com/pingcap/tidb-operator/pull/5448), [@csuzhangxc](https://github.com/csuzhangxc)) + +## Bug 修复 + +- 修复同时变更 annotation 等 meta 信息以及替换 volume 时可能造成 TiDB Operator reconcile 死锁的问题 ([#5382](https://github.com/pingcap/tidb-operator/pull/5382), [@anish-db](https://github.com/anish-db)) +- 修复替换 volume 时可能给 PD member 设置错误的 label 的问题 ([#5393](https://github.com/pingcap/tidb-operator/pull/5393), [@anish-db](https://github.com/anish-db)) From 46e7d44bf036950fcec37cfa36a11e1f267e1ef6 Mon Sep 17 00:00:00 2001 From: csuzhangxc Date: Mon, 15 Jan 2024 07:42:59 +0000 Subject: [PATCH 2/6] fix --- en/releases/release-1.5.2.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/en/releases/release-1.5.2.md b/en/releases/release-1.5.2.md index 9fce65368..e66c2f721 100644 --- a/en/releases/release-1.5.2.md +++ b/en/releases/release-1.5.2.md @@ -10,15 +10,13 @@ TiDB Operator version: 1.5.2 ## New features -- Support replacing volumes for PD, TiKV, and TiDB ([#5150](https://github.com/pingcap/tidb-operator/pull/5150), [@anish-db](https://github.com/anish-db)) - ## Improvements - `startScriptVersion: v2` supports waiting for Pod IP to match the one published to external DNS before starting a PD or TiKV to better support scenarios such as Stale Read ([#5381](https://github.com/pingcap/tidb-operator/pull/5381), [@smineyev81](https://github.com/smineyev81)) -- `startScriptVersion: v2` supports explicitly specifying PD addresses to better support scenarios where TiDB clusters are deployed across Kubernetes ([#5400](https://github.com/pingcap/tidb-operator/pull/5400), [@smineyev81](https://github.com/smineyev81)) +- `startScriptVersion: v2` supports explicitly specifying PD addresses to better support scenarios where a TiDB cluster is deployed across Kubernetes ([#5400](https://github.com/pingcap/tidb-operator/pull/5400), [@smineyev81](https://github.com/smineyev81)) - tidb-operator Helm Chart supports specify resource lock for leader election when deploying Advanced-StatefulSet ([#5448](https://github.com/pingcap/tidb-operator/pull/5448), [@csuzhangxc](https://github.com/csuzhangxc)) ## Bug fixes -- Fixed the issue that changing meta information such as annotations and replacing volume at the same time may cause a deadlock for TiDB Operator reconcile ([#5382](https://github.com/pingcap/tidb-operator/pull/5382), [@anish-db](https://github.com/anish-db)) -- Fixed the issue that the PD member might be set the wrong label when replacing volume ([#5393](https://github.com/pingcap/tidb-operator/pull/5393), [@anish-db](https://github.com/anish-db)) +- Fix the issue that changing meta information such as annotations and replacing volumes at the same time may cause a deadlock for TiDB Operator reconcile ([#5382](https://github.com/pingcap/tidb-operator/pull/5382), [@anish-db](https://github.com/anish-db)) +- Fix the issue that the PD member might be set the wrong label when replacing volumes ([#5393](https://github.com/pingcap/tidb-operator/pull/5393), [@anish-db](https://github.com/anish-db)) From a4e0b9e9181d18a44c27a526fbe329428dd2e294 Mon Sep 17 00:00:00 2001 From: Ran Date: Thu, 18 Jan 2024 18:40:38 +0800 Subject: [PATCH 3/6] Apply suggestions from code review Co-authored-by: BornChanger <97348524+BornChanger@users.noreply.github.com> --- en/releases/release-1.5.2.md | 8 +++++--- zh/releases/release-1.5.2.md | 2 ++ 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/en/releases/release-1.5.2.md b/en/releases/release-1.5.2.md index e66c2f721..787f3bc83 100644 --- a/en/releases/release-1.5.2.md +++ b/en/releases/release-1.5.2.md @@ -10,13 +10,15 @@ TiDB Operator version: 1.5.2 ## New features +Starting from v1.5.2, TiDB Operator supports backing up and restoring the data of a TiDB cluster deployed across multiple AWS Kubernetes clusters to AWS storage using EBS volume snapshots. For more information, refer to [Back up Data Using EBS Snapshots across Multiple Kubernetes](backup-by-ebs-snapshot-across-multiple-kubernetes.md) and [Restore Data Using EBS Snapshots across Multiple Kubernetes](restore-from-ebs-snapshot-across-multiple-kubernetes.md). ([#5003](https://github.com/pingcap/tidb-operator/pull/5003), [@BornChanger](https://github.com/BornChanger), [@WangLe1321](https://github.com/WangLe1321), [@YuJuncen](https://github.com/YuJuncen), [@csuzhangxc](https://github.com/csuzhangxc)) + ## Improvements - `startScriptVersion: v2` supports waiting for Pod IP to match the one published to external DNS before starting a PD or TiKV to better support scenarios such as Stale Read ([#5381](https://github.com/pingcap/tidb-operator/pull/5381), [@smineyev81](https://github.com/smineyev81)) - `startScriptVersion: v2` supports explicitly specifying PD addresses to better support scenarios where a TiDB cluster is deployed across Kubernetes ([#5400](https://github.com/pingcap/tidb-operator/pull/5400), [@smineyev81](https://github.com/smineyev81)) -- tidb-operator Helm Chart supports specify resource lock for leader election when deploying Advanced-StatefulSet ([#5448](https://github.com/pingcap/tidb-operator/pull/5448), [@csuzhangxc](https://github.com/csuzhangxc)) +- tidb-operator Helm Chart supports specifying resource lock for leader election when deploying Advanced StatefulSet ([#5448](https://github.com/pingcap/tidb-operator/pull/5448), [@csuzhangxc](https://github.com/csuzhangxc)) ## Bug fixes -- Fix the issue that changing meta information such as annotations and replacing volumes at the same time may cause a deadlock for TiDB Operator reconcile ([#5382](https://github.com/pingcap/tidb-operator/pull/5382), [@anish-db](https://github.com/anish-db)) -- Fix the issue that the PD member might be set the wrong label when replacing volumes ([#5393](https://github.com/pingcap/tidb-operator/pull/5393), [@anish-db](https://github.com/anish-db)) +- Fix the issue that changing meta information such as annotations and replacing volumes at the same time might cause a deadlock for TiDB Operator reconcile ([#5382](https://github.com/pingcap/tidb-operator/pull/5382), [@anish-db](https://github.com/anish-db)) +- Fix the issue that the PD member might be set to the wrong label when replacing volumes ([#5393](https://github.com/pingcap/tidb-operator/pull/5393), [@anish-db](https://github.com/anish-db)) diff --git a/zh/releases/release-1.5.2.md b/zh/releases/release-1.5.2.md index 45b0725d8..30fd56b7d 100644 --- a/zh/releases/release-1.5.2.md +++ b/zh/releases/release-1.5.2.md @@ -10,6 +10,8 @@ TiDB Operator 版本：1.5.2 ## 新功能 +从 v1.5.2 起, TiDB operator 支持基于 AWS EBS 快照的备份能力的跨多个 K8S 集群的备份恢复。更多详情，请查看文档 [Back up Data Using EBS Snapshots across Multiple Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/stable/backup-by-ebs-snapshot-across-multiple-kubernetes) 和 [Restore Data Using EBS Snapshots across Multiple Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/stable/restore-from-ebs-snapshot-across-multiple-kubernetes)。([#5003](https://github.com/pingcap/tidb-operator/pull/5003), [@BornChanger](https://github.com/BornChanger), [@WangLe1321](https://github.com/WangLe1321), [@YuJuncen](https://github.com/YuJuncen), [@csuzhangxc](https://github.com/csuzhangxc)) + ## 优化提升 - `startScriptVersion: v2` 支持在重启 PD、TiKV 时等待 Pod IP 与 DNS 解析一致后再进行启动以更好地支持 Stale Read 等场景 ([#5381](https://github.com/pingcap/tidb-operator/pull/5381), [@smineyev81](https://github.com/smineyev81)) From 1a600b6d68949e31a27b5b143272965dd215e362 Mon Sep 17 00:00:00 2001 From: Ran Date: Thu, 18 Jan 2024 18:40:56 +0800 Subject: [PATCH 4/6] Update zh/releases/release-1.5.2.md --- zh/releases/release-1.5.2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/releases/release-1.5.2.md b/zh/releases/release-1.5.2.md index 30fd56b7d..77decf1b1 100644 --- a/zh/releases/release-1.5.2.md +++ b/zh/releases/release-1.5.2.md @@ -4,7 +4,7 @@ title: TiDB Operator 1.5.2 Release Notes # TiDB Operator 1.5.2 Release Notes -发布日期: 2024 年 1 月 19 日 +发布日期：2024 年 1 月 19 日 TiDB Operator 版本：1.5.2 From bfb7898ec50f58589576ea9babf54f135a5f6331 Mon Sep 17 00:00:00 2001 From: Ran Date: Thu, 18 Jan 2024 18:41:23 +0800 Subject: [PATCH 5/6] Update zh/releases/release-1.5.2.md --- zh/releases/release-1.5.2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zh/releases/release-1.5.2.md b/zh/releases/release-1.5.2.md index 77decf1b1..a93c746bf 100644 --- a/zh/releases/release-1.5.2.md +++ b/zh/releases/release-1.5.2.md @@ -10,7 +10,7 @@ TiDB Operator 版本：1.5.2 ## 新功能 -从 v1.5.2 起, TiDB operator 支持基于 AWS EBS 快照的备份能力的跨多个 K8S 集群的备份恢复。更多详情，请查看文档 [Back up Data Using EBS Snapshots across Multiple Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/stable/backup-by-ebs-snapshot-across-multiple-kubernetes) 和 [Restore Data Using EBS Snapshots across Multiple Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/stable/restore-from-ebs-snapshot-across-multiple-kubernetes)。([#5003](https://github.com/pingcap/tidb-operator/pull/5003), [@BornChanger](https://github.com/BornChanger), [@WangLe1321](https://github.com/WangLe1321), [@YuJuncen](https://github.com/YuJuncen), [@csuzhangxc](https://github.com/csuzhangxc)) +从 v1.5.2 起，TiDB Operator 支持基于 AWS EBS 快照的备份能力的跨多个 K8S 集群的备份恢复。更多详情，请查看文档 [Back up Data Using EBS Snapshots across Multiple Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/stable/backup-by-ebs-snapshot-across-multiple-kubernetes) 和 [Restore Data Using EBS Snapshots across Multiple Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/stable/restore-from-ebs-snapshot-across-multiple-kubernetes)。([#5003](https://github.com/pingcap/tidb-operator/pull/5003), [@BornChanger](https://github.com/BornChanger), [@WangLe1321](https://github.com/WangLe1321), [@YuJuncen](https://github.com/YuJuncen), [@csuzhangxc](https://github.com/csuzhangxc)) ## 优化提升 From de1cbe5ab528952e3b558fcec13db55346689d98 Mon Sep 17 00:00:00 2001 From: Ran Date: Fri, 19 Jan 2024 14:38:42 +0800 Subject: [PATCH 6/6] Update en/releases/release-1.5.2.md --- en/releases/release-1.5.2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/releases/release-1.5.2.md b/en/releases/release-1.5.2.md index 787f3bc83..71005f28c 100644 --- a/en/releases/release-1.5.2.md +++ b/en/releases/release-1.5.2.md @@ -10,7 +10,7 @@ TiDB Operator version: 1.5.2 ## New features -Starting from v1.5.2, TiDB Operator supports backing up and restoring the data of a TiDB cluster deployed across multiple AWS Kubernetes clusters to AWS storage using EBS volume snapshots. For more information, refer to [Back up Data Using EBS Snapshots across Multiple Kubernetes](backup-by-ebs-snapshot-across-multiple-kubernetes.md) and [Restore Data Using EBS Snapshots across Multiple Kubernetes](restore-from-ebs-snapshot-across-multiple-kubernetes.md). ([#5003](https://github.com/pingcap/tidb-operator/pull/5003), [@BornChanger](https://github.com/BornChanger), [@WangLe1321](https://github.com/WangLe1321), [@YuJuncen](https://github.com/YuJuncen), [@csuzhangxc](https://github.com/csuzhangxc)) +Starting from v1.5.2, TiDB Operator supports backing up and restoring the data of a TiDB cluster deployed across multiple AWS Kubernetes clusters to AWS storage using EBS volume snapshots. For more information, refer to [Back up Data Using EBS Snapshots across Multiple Kubernetes](../backup-by-ebs-snapshot-across-multiple-kubernetes.md) and [Restore Data Using EBS Snapshots across Multiple Kubernetes](../restore-from-ebs-snapshot-across-multiple-kubernetes.md). ([#5003](https://github.com/pingcap/tidb-operator/pull/5003), [@BornChanger](https://github.com/BornChanger), [@WangLe1321](https://github.com/WangLe1321), [@YuJuncen](https://github.com/YuJuncen), [@csuzhangxc](https://github.com/csuzhangxc)) ## Improvements