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.1.7 #845

Merged
merged 10 commits into from
Nov 14, 2020
1 change: 1 addition & 0 deletions en/TOC.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,7 @@
+ [TiDB Operator Roadmap](roadmap.md)
+ Release Notes
+ v1.1
- [1.1.7](releases/release-1.1.7.md)
- [1.1.6](releases/release-1.1.6.md)
- [1.1.5](releases/release-1.1.5.md)
- [1.1.4](releases/release-1.1.4.md)
Expand Down
35 changes: 35 additions & 0 deletions en/releases/release-1.1.7.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
---
title: TiDB Operator 1.1.7 Release Notes
---

# TiDB Operator 1.1.7 Release Notes

Release date: November 13, 2020

TiDB Operator version: 1.1.7

## New Features

- Support `spec.toolImage` for Backup & Restore with BR to define the image used to provide the BR binary executables, use `pingcap/br:${tikv_version}` by default ([#3471](https://github.com/pingcap/tidb-operator/pull/3471), [@namco1992](https://github.com/namco1992))
dragonly marked this conversation as resolved.
Show resolved Hide resolved
- Add `spec.pd.storageVolumes` and `spec.tidb.storageVolumes` to support mounting multiple PVs for PD and TiDB ([#3444](https://github.com/pingcap/tidb-operator/pull/3444), [@mikechengwei](https://github.com/mikechengwei))
- Add `spec.tikv.storageVolumes` to support mounting multiple PVs for TiKV ([#3425](https://github.com/pingcap/tidb-operator/pull/3425), [@mikechengwei](https://github.com/mikechengwei))
dragonly marked this conversation as resolved.
Show resolved Hide resolved
- Add `spec.tidb.readinessProbe` config to support requesting `127.0.0.0:10080/status` for TiDB's readiness probe, TiDB version >= v4.0.9 required ([#3438](https://github.com/pingcap/tidb-operator/pull/3438), [@july2993](https://github.com/july2993))
- Support the case where advanced statefulset controller is enabled during PD leader transfer ([#3395](https://github.com/pingcap/tidb-operator/pull/3395), [@tangwz](https://github.com/tangwz))
dragonly marked this conversation as resolved.
Show resolved Hide resolved
- Support setting `OnDelete` update strategies for the StatefulSets via `spec.statefulSetUpdateStrategy` in the TidbCluster CR ([#3408](https://github.com/pingcap/tidb-operator/pull/3408), [@cvvz](https://github.com/cvvz))
- Support HA scheduling when failover happens ([#3419](https://github.com/pingcap/tidb-operator/pull/3419), [@cvvz](https://github.com/cvvz))
- Support smooth migration from TiDB clusters deployed with TiDB Ansible or TiUP or in the same Kubernetes cluster ([#3226](https://github.com/pingcap/tidb-operator/pull/3226), [@cvvz](https://github.com/cvvz))
- tidb-scheduler supports advanced StatefulSet ([#3388](https://github.com/pingcap/tidb-operator/pull/3388), [@cvvz](https://github.com/cvvz))

## Improvements

- Forbid to scale in TiKV when the number of UP stores is equal to or less than 3 ([#3367](https://github.com/pingcap/tidb-operator/pull/3367), [@cvvz](https://github.com/cvvz))
- `phase` is added in `BackupStatus` and `RestoreStatus`, it will be in sync with the latest condition type and shown when doing `kubectl get` ([#3397](https://github.com/pingcap/tidb-operator/pull/3397), [@namco1992](https://github.com/namco1992))
dragonly marked this conversation as resolved.
Show resolved Hide resolved
- Skip setting `tikv_gc_life_time` via SQL for backup and restore with BR when the TiKV version >= v4.0.8 ([#3443](https://github.com/pingcap/tidb-operator/pull/3443), [@namco1992](https://github.com/namco1992))

## Bug Fixes

- Fix the issue that PD cannot scale in to 0 even if there are other PD members outside of this TidbCluster ([#3456](https://github.com/pingcap/tidb-operator/pull/3456), [@dragonly](https://github.com/dragonly))
dragonly marked this conversation as resolved.
Show resolved Hide resolved

## Notable Changes
dragonly marked this conversation as resolved.
Show resolved Hide resolved

- The behavior of `prometheus.spec.config.commandOptions` has changed. Any duplicated flags must be removed or Prometheus will fail to start ([#3390](https://github.com/pingcap/tidb-operator/pull/3390), [@mightyguava](https://github.com/mightyguava))