Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

en,zh: add v1.5.2 release notes #2485

Merged
merged 6 commits into from
Jan 19, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions en/TOC.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down
24 changes: 24 additions & 0 deletions en/releases/release-1.5.2.md
Original file line number Diff line number Diff line change
@@ -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
ran-huang marked this conversation as resolved.
Show resolved Hide resolved

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 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 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))
1 change: 1 addition & 0 deletions zh/TOC.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down
24 changes: 24 additions & 0 deletions zh/releases/release-1.5.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
---
title: TiDB Operator 1.5.2 Release Notes
---

# TiDB Operator 1.5.2 Release Notes

发布日期:2024 年 1 月 19 日

TiDB Operator 版本:1.5.2

## 新功能
ran-huang marked this conversation as resolved.
Show resolved Hide resolved

从 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))
- `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))
Loading