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 release notes for v1.3.0-beta.1 #1589

Merged
merged 11 commits into from
Jan 12, 2022

Conversation

just1900
Copy link
Contributor

@just1900 just1900 commented Jan 12, 2022

First-time contributors' checklist

What is changed, added, or deleted? (Required)

Which TiDB Operator version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v1.2 (TiDB Operator 1.2 versions)
  • v1.1 (TiDB Operator 1.1 versions)
  • v1.0 (TiDB Operator 1.0 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot
Copy link
Member

ti-chi-bot commented Jan 12, 2022

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • DanielZhangQD
  • ran-huang

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added missing-translation-status This PR does not have translation status info. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 12, 2022
Co-authored-by: Shiori <yshshihaoren@qq.com>
zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved
zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved
zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved
zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved

## 滚动升级改动

- 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更,如果使用小于或等与 v1.2 operator 部署了 v5.4 版本的 TidbCluster,升级 Operator 到 1.3.0-beta.1 版本会导致 Tiflash 组件滚动升级
Copy link
Contributor

@DanielZhangQD DanielZhangQD Jan 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更,如果使用小于或等与 v1.2 operator 部署了 v5.4 版本的 TidbCluster,升级 Operator 到 1.3.0-beta.1 版本会导致 Tiflash 组件滚动升级
- 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更,如果使用 v1.2.x 版本 TiDB Operator,部署 >= v5.4.x 版本 TiDB 集群,升级 TiDB Operator 到 v1.3.0-beta.1 版本会导致 TiFlash 组件滚动更新。建议在升级 TiDB v5.4.x 之前先升级 TiDB Operator 到 v1.3.x

## 滚动升级改动

- 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更,如果使用小于或等与 v1.2 operator 部署了 v5.4 版本的 TidbCluster,升级 Operator 到 1.3.0-beta.1 版本会导致 Tiflash 组件滚动升级
- 由于 [#4169](https://github.com/pingcap/tidb-operator/pull/4169) 的变更,如果部署了大于或等于 v5.0.0 版本的 TidbCluster 并且设置了 `seperateRocksDBLog` 字段值为`true`,升级 Operator 到 1.3.0-beta.1 版本会导致 TiKV 组件滚动升级
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 由于 [#4169](https://github.com/pingcap/tidb-operator/pull/4169) 的变更,如果部署了大于或等于 v5.0.0 版本的 TidbCluster 并且设置了 `seperateRocksDBLog` 字段值为`true`,升级 Operator 到 1.3.0-beta.1 版本会导致 TiKV 组件滚动升级
- 由于 [#4169](https://github.com/pingcap/tidb-operator/pull/4169) 的变更,如果 TiDB 集群版本 >= v5.0.x 并且设置了 `spec.tikv.seperateRocksDBLog: true` 或者 `spec.tikv.separateRaftLog: true`,升级 TiDB Operator 到 v1.3.0-beta.1 版本会导致 TiKV 组件滚动更新

zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved

## 滚动升级改动

- 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更,如果使用小于或等与 v1.2 operator 部署了 v5.4 版本的 TidbCluster,升级 Operator 到 1.3.0-beta.1 版本会导致 Tiflash 组件滚动升级
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更,如果使用小于或等与 v1.2 operator 部署了 v5.4 版本的 TidbCluster,升级 Operator 到 1.3.0-beta.1 版本会导致 Tiflash 组件滚动升级
- 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更,如果使用 v1.2 及更早版本的 TiDB Operator 部署了 v5.4 版本的 TidbCluster,升级 TiDB Operator 到 1.3.0-beta.1 版本会导致 TiFlash 组件滚动升级

## 滚动升级改动

- 由于 [#4358](https://github.com/pingcap/tidb-operator/pull/4358) 的变更,如果使用小于或等与 v1.2 operator 部署了 v5.4 版本的 TidbCluster,升级 Operator 到 1.3.0-beta.1 版本会导致 Tiflash 组件滚动升级
- 由于 [#4169](https://github.com/pingcap/tidb-operator/pull/4169) 的变更,如果部署了大于或等于 v5.0.0 版本的 TidbCluster 并且设置了 `seperateRocksDBLog` 字段值为`true`,升级 Operator 到 1.3.0-beta.1 版本会导致 TiKV 组件滚动升级
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 由于 [#4169](https://github.com/pingcap/tidb-operator/pull/4169) 的变更,如果部署了大于或等于 v5.0.0 版本的 TidbCluster 并且设置了 `seperateRocksDBLog` 字段值为`true`,升级 Operator 到 1.3.0-beta.1 版本会导致 TiKV 组件滚动升级
- 由于 [#4169](https://github.com/pingcap/tidb-operator/pull/4169) 的变更,如果部署了 v5.0.0 及更新版本的 TidbCluster 并且设置了 `seperateRocksDBLog` 字段值为 `true`,升级 TiDB Operator 到 1.3.0-beta.1 版本会导致 TiKV 组件滚动升级

Comment on lines 29 to 30
- 为跨 Kubernetes 集群部署的 TidbCluster 添加 e2e 测试用例([#4354](https://github.com/pingcap/tidb-operator/pull/4354), [#4352](https://github.com/pingcap/tidb-operator/pull/4352), [#4314](https://github.com/pingcap/tidb-operator/pull/4314), [#4300](https://github.com/pingcap/tidb-operator/pull/4300), [@just1900](https://github.com/just1900))
- 为跨 Kubernetes 集群部署的 TidbCluster 添加部署和删除集群的 e2e 测试用例 ([#4289](https://github.com/pingcap/tidb-operator/pull/4289), [@handlerww](https://github.com/handlerww))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

测试用例跟用户无关,删掉吧

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这里留一条 跨 Kubernetes 部署功能 GA 就行


## 优化提升

- 由于 v5.4.0 版本 TiFlash 的配置变动,Operator 中去除和变更了一些 TiFlash 的默认配置。如果使用 v1.2 operator 部署了 v5.4 版本的 TidbCluster,升级 Operator 到 1.3.0-beta.1 版本会导致 Tiflash 组件滚动升级 ([#4358](https://github.com/pingcap/tidb-operator/pull/4358), [@KanShiori](https://github.com/KanShiori))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 由于 v5.4.0 版本 TiFlash 的配置变动,Operator 中去除和变更了一些 TiFlash 的默认配置。如果使用 v1.2 operator 部署了 v5.4 版本的 TidbCluster,升级 Operator 到 1.3.0-beta.1 版本会导致 Tiflash 组件滚动升级 ([#4358](https://github.com/pingcap/tidb-operator/pull/4358), [@KanShiori](https://github.com/KanShiori))
- 由于 v5.4.0 版本 TiFlash 的配置变动,TiDB Operator 中去除和变更了一些 TiFlash 的默认配置。如果使用 v1.2 及更早版本的 TiDB Operator 部署了 v5.4 版本的 TidbCluster,升级 TiDB Operator 到 1.3.0-beta.1 版本会导致 TiFlash 组件滚动升级 ([#4358](https://github.com/pingcap/tidb-operator/pull/4358), [@KanShiori](https://github.com/KanShiori))

- 为跨 Kubernetes 集群部署的 TidbCluster 添加 e2e 测试用例([#4354](https://github.com/pingcap/tidb-operator/pull/4354), [#4352](https://github.com/pingcap/tidb-operator/pull/4352), [#4314](https://github.com/pingcap/tidb-operator/pull/4314), [#4300](https://github.com/pingcap/tidb-operator/pull/4300), [@just1900](https://github.com/just1900))
- 为跨 Kubernetes 集群部署的 TidbCluster 添加部署和删除集群的 e2e 测试用例 ([#4289](https://github.com/pingcap/tidb-operator/pull/4289), [@handlerww](https://github.com/handlerww))
- 优化:废弃 pod 的 validating 和 mutating webhook ([#4209](https://github.com/pingcap/tidb-operator/pull/4209), [@mianhk](https://github.com/mianhk))
- 在 TidbMonitor controller 中去除对 firstTC 和 firstDC 的依赖 ([#4272](https://github.com/pingcap/tidb-operator/pull/4272), [@mikechengwei](https://github.com/mikechengwei))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这个对用户的直接优化提升是什么?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

删掉就行

Comment on lines 34 to 35
- 分离 dm 和 TidbMonitor 的代码逻辑 ([#4243](https://github.com/pingcap/tidb-operator/pull/4243), [@mikechengwei](https://github.com/mikechengwei))
- 优化 secret 的查询逻辑 ([#4166](https://github.com/pingcap/tidb-operator/pull/4166), [@mianhk](https://github.com/mianhk))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

用户不需要知道这些吧

zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved
zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved
zh/releases/release-1.3.0-beta.1.md Outdated Show resolved Hide resolved
Co-authored-by: Ran <huangran@pingcap.com>

- 允许设置所有组件的最小副本数为 0 ([#4288](https://github.com/pingcap/tidb-operator/pull/4288), [@handlerww](https://github.com/handlerww))
- 升级 Grafana 镜像版本为 7.5.11,提升安全性 ([#4212](https://github.com/pingcap/tidb-operator/pull/4212), [@makocchi-git](https://github.com/makocchi-git))
- 废弃 pod 的 validating 和 mutating webhook ([#4209](https://github.com/pingcap/tidb-operator/pull/4209), [@mianhk](https://github.com/mianhk))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这个要单独列一条二级标题 @ran-huang 有啥建议吗?

just1900 and others added 2 commits January 12, 2022 17:05
Co-authored-by: Ran <huangran@pingcap.com>
Co-authored-by: DanielZhangQD <36026334+DanielZhangQD@users.noreply.github.com>
@ti-chi-bot ti-chi-bot removed the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 12, 2022
@ti-chi-bot ti-chi-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 12, 2022
Signed-off-by: Ran <huangran@pingcap.com>
- Use `secretRef` to obtain Grafana password in TidbMonitor to avoid using plaintext password. ([#4135](https://github.com/pingcap/tidb-operator/pull/4135), [@mianhk](https://github.com/mianhk))
- Optimize the upgrade process for PD and TiKV components with fewer than two replicas, and force the upgrade of PD and TiKV components by default to avoid the upgrade process from taking too long ([#4107](https://github.com/pingcap/tidb-operator/pull/4107), [#4091](https://github.com/pingcap/tidb-operator/pull/4091), [@mianhk](https://github.com/mianhk))

## Other Notable Changes
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这些改进不能移进新功能改进提升吗?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

可以

Copy link
Contributor

@DanielZhangQD DanielZhangQD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label Jan 12, 2022
@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Jan 12, 2022
@ran-huang ran-huang added the translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. label Jan 12, 2022
@ti-chi-bot ti-chi-bot removed the missing-translation-status This PR does not have translation status info. label Jan 12, 2022
@ran-huang ran-huang added the v1.3 label Jan 12, 2022
@DanielZhangQD
Copy link
Contributor

/merge

@ti-chi-bot
Copy link
Member

This pull request has been accepted and is ready to merge.

Commit hash: 378984e

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jan 12, 2022
@ti-chi-bot ti-chi-bot merged commit df526cb into pingcap:master Jan 12, 2022
@just1900 just1900 deleted the add-1.3.0-beta.1-release-noets branch January 13, 2022 06:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. v1.3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants