pingcap · ti-chi-bot · Mar 27, 2024 · Mar 22, 2024 · Mar 22, 2024 · Mar 22, 2024
diff --git a/en/TOC.md b/en/TOC.md
@@ -125,6 +125,8 @@
   - [Monitoring and Alert on Kubernetes](monitor-kubernetes.md)
   - [PingCAP Clinic Diagnostic Data](clinic-data-collection.md)
 - Release Notes
+  - v1.6
+    - [1.6.0-beta.1](releases/release-1.6.0-beta.1.md)
   - v1.5
     - [1.5.2](releases/release-1.5.2.md)
     - [1.5.1](releases/release-1.5.1.md)

diff --git a/en/releases/release-1.6.0-beta.1.md b/en/releases/release-1.6.0-beta.1.md
@@ -0,0 +1,29 @@
+---
+title: TiDB Operator 1.6.0-beta.1 Release Notes
+summary: Learn about new features, improvements, and bug fixes in TiDB Operator 1.6.0-beta.1.
+---
+
+# TiDB Operator 1.6.0-beta.1 Release Notes
+
+Release date: March 27, 2024
+
+TiDB Operator version: 1.6.0-beta.1
+
+## New features
+
+- Support deploying PD v8.0.0 and later versions in [microservice mode](https://docs.pingcap.com/tidb/dev/pd-microservices) (experimental) ([#5398](https://github.com/pingcap/tidb-operator/pull/5398), [@HuSharp](https://github.com/HuSharp))
+- Support scaling out or in TiDB components in parallel ([#5570](https://github.com/pingcap/tidb-operator/pull/5570), [@csuzhangxc](https://github.com/csuzhangxc))
+- Support setting `livenessProbe` and `readinessProbe` for the Discovery component ([#5565](https://github.com/pingcap/tidb-operator/pull/5565), [@csuzhangxc](https://github.com/csuzhangxc))
+- Support setting `startupProbe` for TiDB components ([#5588](https://github.com/pingcap/tidb-operator/pull/5588), [@fgksgf](https://github.com/fgksgf))
+
+## Improvements
+
+- Upgrade Kubernetes dependency to v1.28, and it is not recommended to deploy tidb-scheduler ([#5495](https://github.com/pingcap/tidb-operator/pull/5495), [@csuzhangxc](https://github.com/csuzhangxc))
+- When deploying using Helm chart, support setting lock resource used by tidb-controller-manager for leader election, with the default value of `.Values.controllerManager.leaderResourceLock: leases`. When upgrading from versions before v1.6 to v1.6.0-beta.1 and later versions, it is recommended to first set `.Values.controllerManager.leaderResourceLock: endpointsleases` and wait for the new tidb-controller-manager to run normally before setting it to `.Values.controllerManager.leaderResourceLock: leases` to update the deployment ([#5450](https://github.com/pingcap/tidb-operator/pull/5450), [@csuzhangxc](https://github.com/csuzhangxc))
+- Support for TiFlash to directly mount ConfigMap without relying on an InitContainer to process configuration files ([#5552](https://github.com/pingcap/tidb-operator/pull/5552), [@ideascf](https://github.com/ideascf))
+- Add check for `resources.request.storage` in the `storageClaims` configuration of TiFlash ([#5489](https://github.com/pingcap/tidb-operator/pull/5489), [@unw9527](https://github.com/unw9527))
+
+## Bug fixes
+
+- Fix the issue that the `tikv-min-ready-seconds` check is not performed on the last TiKV Pod during a rolling restart of TiKV ([#5544](https://github.com/pingcap/tidb-operator/pull/5544), [@wangz1x](https://github.com/wangz1x))
+- Fix the issue that the TiDB cluster cannot start when only non-`cluster.local` clusterDomain TLS certificates are available ([#5560](https://github.com/pingcap/tidb-operator/pull/5560), [@csuzhangxc](https://github.com/csuzhangxc))
diff --git a/en/tidb-operator-overview.md b/en/tidb-operator-overview.md
@@ -13,7 +13,8 @@ The corresponding relationship between TiDB Operator and TiDB versions is as fol
 | TiDB versions | Compatible TiDB Operator versions |
 |:---|:---|
 | dev               | dev                 |
-| TiDB >= 7.1       | 1.5 (Recommended), 1.4 |
+| TiDB >= 8.0       | 1.6 (Recommended), 1.5 |
+| 7.1 <= TiDB < 8.0 | 1.5 (Recommended), 1.4 |
 | 6.5 <= TiDB < 7.1 | 1.5, 1.4 (Recommended), 1.3 |
 | 5.4 <= TiDB < 6.5 | 1.4, 1.3 (Recommended)   |
 | 5.1 <= TiDB < 5.4 | 1.4, 1.3 (Recommended), 1.2      |

diff --git a/en/tidb-scheduler.md b/en/tidb-scheduler.md
@@ -8,6 +8,10 @@ aliases: ['/docs/tidb-in-kubernetes/dev/tidb-scheduler/']
 
 TiDB Scheduler is a TiDB implementation of [Kubernetes scheduler extender](https://github.com/kubernetes/design-proposals-archive/blob/main/scheduling/scheduler_extender.md). TiDB Scheduler is used to add new scheduling rules to Kubernetes. This document introduces these new scheduling rules and how TiDB Scheduler works.
 
+> **Note:**
+>
+> Starting from TiDB Operator v1.6, it is not recommended to deploy TiDB Scheduler.
+
 ## tidb-scheduler and default-scheduler
 
 A [kube-scheduler](https://kubernetes.io/zh/docs/concepts/scheduling-eviction/kube-scheduler/) is deployed by default in the Kubernetes cluster for Pod scheduling. The default scheduler name is `default-scheduler`.

diff --git a/zh/TOC.md b/zh/TOC.md
@@ -125,6 +125,8 @@
   - [Kubernetes 监控与告警](monitor-kubernetes.md)
   - [PingCAP Clinic 数据采集范围说明](clinic-data-collection.md)
 - 版本发布历史
+  - v1.6
+    - [1.6.0-beta.1](releases/release-1.6.0-beta.1.md)
   - v1.5
     - [1.5.2](releases/release-1.5.2.md)
     - [1.5.1](releases/release-1.5.1.md)

diff --git a/zh/releases/release-1.6.0-beta.1.md b/zh/releases/release-1.6.0-beta.1.md
@@ -0,0 +1,29 @@
+---
+title: TiDB Operator 1.6.0-beta.1 Release Notes
+summary: 了解 TiDB Operator 1.6.0-beta.1 版本的新功能、优化提升，以及 Bug 修复。
+---
+
+# TiDB Operator 1.6.0-beta.1 Release Notes
+
+发布日期：2024 年 3 月 27 日
+
+TiDB Operator 版本：1.6.0-beta.1
+
+## 新功能
+
+- 支持以[微服务模式](https://docs.pingcap.com/zh/tidb/dev/pd-microservices)部署 PD v8.0.0 及以上版本（实验特性）([#5398](https://github.com/pingcap/tidb-operator/pull/5398), [@HuSharp](https://github.com/HuSharp))
+- 支持对 TiDB 组件进行并行的扩容与缩容操作 ([#5570](https://github.com/pingcap/tidb-operator/pull/5570), [@csuzhangxc](https://github.com/csuzhangxc))
+- 支持为 Discovery 组件设置 `livenessProbe` 与 `readinessProbe` ([#5565](https://github.com/pingcap/tidb-operator/pull/5565), [@csuzhangxc](https://github.com/csuzhangxc))
+- 支持为 TiDB 组件设置 `startupProbe` ([#5588](https://github.com/pingcap/tidb-operator/pull/5588), [@fgksgf](https://github.com/fgksgf))
+
+## 优化提升
+
+- 升级 Kubernetes 依赖库至 v1.28 版本，建议不再部署 tidb-scheduler ([#5495](https://github.com/pingcap/tidb-operator/pull/5495), [@csuzhangxc](https://github.com/csuzhangxc))
+- 通过 Helm Chart 部署时支持设置 tidb-controller-manager 用于 leader 选举的 lock resource，默认值为 `.Values.controllerManager.leaderResourceLock: leases`。当从 v1.6 之前的版本升级到 v1.6.0-beta.1 及之后的版本时，推荐先设置 `.Values.controllerManager.leaderResourceLock: endpointsleases` 并待新的 tidb-controller-manager 正常运行后再设置为 `.Values.controllerManager.leaderResourceLock: leases` 以更新部署 ([#5450](https://github.com/pingcap/tidb-operator/pull/5450), [@csuzhangxc](https://github.com/csuzhangxc))
+- 支持为 TiFlash 直接挂载 ConfigMap 而不再依赖 InitContainer 对配置文件进行处理 ([#5552](https://github.com/pingcap/tidb-operator/pull/5552), [@ideascf](https://github.com/ideascf))
+- 增加对 TiFlash `storageClaims` 配置中 `resources.request.storage` 的检查 ([#5489](https://github.com/pingcap/tidb-operator/pull/5489), [@unw9527](https://github.com/unw9527))
+
+## Bug 修复
+
+- 修复滚动重启 TiKV 时，没有对最后一个 TiKV Pod 执行 `tikv-min-ready-seconds` 检查的问题 ([#5544](https://github.com/pingcap/tidb-operator/pull/5544), [@wangz1x](https://github.com/wangz1x))
+- 修复仅能使用非 `cluster.local` clusterDomain 的 TLS 证书时 TiDB 集群无法启动的问题 ([#5560](https://github.com/pingcap/tidb-operator/pull/5560), [@csuzhangxc](https://github.com/csuzhangxc))
diff --git a/zh/tidb-operator-overview.md b/zh/tidb-operator-overview.md
@@ -13,7 +13,8 @@ TiDB Operator 与适用的 TiDB 版本的对应关系如下：
 | TiDB 版本 | 适用的 TiDB Operator 版本 |
 |:---|:---|
 | dev               | dev                 |
-| TiDB >= 7.1       | 1.5（推荐），1.4 |
+| TiDB >= 8.0       | 1.6（推荐），1.5 |
+| 7.1 <= TiDB < 8.0 | 1.5（推荐），1.4 |
 | 6.5 <= TiDB < 7.1 | 1.5, 1.4（推荐），1.3     |
 | 5.4 <= TiDB < 6.5 | 1.4, 1.3（推荐）   |
 | 5.1 <= TiDB < 5.4 | 1.4，1.3（推荐），1.2      |

diff --git a/zh/tidb-scheduler.md b/zh/tidb-scheduler.md
@@ -8,6 +8,10 @@ aliases: ['/docs-cn/tidb-in-kubernetes/dev/tidb-scheduler/']
 
 TiDB Scheduler 是 [Kubernetes 调度器扩展](https://github.com/kubernetes/design-proposals-archive/blob/main/scheduling/scheduler_extender.md) 的 TiDB 实现。TiDB Scheduler 用于向 Kubernetes 添加新的调度规则。本文介绍 TiDB Scheduler 扩展调度器的工作原理。
 
+> **注意：**
+>
+> 从 TiDB Operator v1.6 开始，不推荐部署 TiDB Scheduler。
+
 ## tidb-scheduler 与 default-scheduler
 
 Kubernetes 集群中默认会部署一个 [kube-scheduler](https://kubernetes.io/zh/docs/concepts/scheduling-eviction/kube-scheduler/)，用于 Pod 调度，默认调度器名字为 `default-scheduler`。