From 894c2ecb199b9598915f9e090ea3ab544ef5c173 Mon Sep 17 00:00:00 2001 From: Yecheng Fu Date: Mon, 27 Jul 2020 17:37:45 +0800 Subject: [PATCH] cherry pick #3022 to release-1.1 Signed-off-by: ti-srebot --- CHANGELOG-1.1.md | 32 ++++++++++++++++++++++++++++++++ charts/tidb-cluster/values.yaml | 2 +- charts/tidb-operator/values.yaml | 4 ++-- deploy/aliyun/variables.tf | 2 +- deploy/aws/variables.tf | 2 +- deploy/gcp/variables.tf | 2 +- 6 files changed, 38 insertions(+), 6 deletions(-) diff --git a/CHANGELOG-1.1.md b/CHANGELOG-1.1.md index bcc92ce670..f353759a09 100644 --- a/CHANGELOG-1.1.md +++ b/CHANGELOG-1.1.md @@ -1,3 +1,35 @@ +# TiDB Operator v1.1.3 Release Notes + +## Action Required + +- Add a field `cleanPolicy` in `BackupSpec` to denote the clean policy for backup data when the Backup CR is deleted from the cluster (default to `Retain`). Note that before v1.1.3, TiDB Operator will clean the backup data in the remote storage when the Backup CR is deleted, so if you want to clean backup data as before, set `spec.cleanPolicy` in `Backup` CR or `spec.backupTemplate.cleanPolicy` in `BackupSchedule` CR to `Delete`. ([#3002](https://github.com/pingcap/tidb-operator/pull/3002), [@lichunzhu](https://github.com/lichunzhu)) +- Replace `mydumper` with `dumpling` for backup. + If `spec.mydumper` is configured in the `Backup` CR or `spec.backupTemplate.mydumper` is configured in the `BackupSchedule` CR, migrate it to `spec.dumpling` or `spec.backupTemplate.dumpling`. After you upgrade TiDB Operator to v1.1.3, note that `spec.mydumper` or `spec.backupTemplate.mydumper` will be lost after the upgrade. ([#2870](https://github.com/pingcap/tidb-operator/pull/2870), [@lichunzhu](https://github.com/lichunzhu)) + + +## Other Notable Changes + +- Update tools in backup manager to v4.0.3 ([#3019](https://github.com/pingcap/tidb-operator/pull/3019), [@lichunzhu](https://github.com/lichunzhu)) +- Support `cleanPolicy` for the `Backup` CR to define the clean behavior of the backup data in the remote storage when the `Backup` CR is deleted ([#3002](https://github.com/pingcap/tidb-operator/pull/3002), [@lichunzhu](https://github.com/lichunzhu)) +- Add TLS support for TiCDC ([#3011](https://github.com/pingcap/tidb-operator/pull/3011), [@weekface](https://github.com/weekface)) +- Add TLS support between Drainer and the downstream database server ([#2993](https://github.com/pingcap/tidb-operator/pull/2993), [@lichunzhu](https://github.com/lichunzhu)) +- Support specifying `mysqlNodePort` and `statusNodePort` for TiDB Service Spec ([#2941](https://github.com/pingcap/tidb-operator/pull/2941), [@lichunzhu](https://github.com/lichunzhu)) +- Fix the `initialCommitTs` bug in Drainer's `values.yaml` ([#2857](https://github.com/pingcap/tidb-operator/pull/2857), [@weekface](https://github.com/weekface)) +- Add `backup` config for TiKV server, add `enable-telemetry`, and deprecate `disable-telemetry` config for PD server ([#2964](https://github.com/pingcap/tidb-operator/pull/2964), [@lichunzhu](https://github.com/lichunzhu)) +- Add commitTS info column in `get restore` command ([#2926](https://github.com/pingcap/tidb-operator/pull/2926), [@lichunzhu](https://github.com/lichunzhu)) +- Update the used Grafana version from v6.0.1 to v6.1.6 ([#2923](https://github.com/pingcap/tidb-operator/pull/2923), [@lichunzhu](https://github.com/lichunzhu)) +- Support showing commitTS in restore status ([#2899](https://github.com/pingcap/tidb-operator/pull/2899), [@lichunzhu](https://github.com/lichunzhu)) +- Exit without error if the backup data the user tries to clean does not exist ([#2916](https://github.com/pingcap/tidb-operator/pull/2916), [@lichunzhu](https://github.com/lichunzhu)) +- Support auto-scaling by storage for TiKV in `TidbClusterAutoScaler` ([#2884](https://github.com/pingcap/tidb-operator/pull/2884), [@Yisaer](https://github.com/Yisaer)) +- Clean temporary files in `Backup` job with `Dumpling` to save space ([#2897](https://github.com/pingcap/tidb-operator/pull/2897), [@lichunzhu](https://github.com/lichunzhu)) +- Fail the backup job if existing PVC's size is smaller than the storage request in the backup job ([#2894](https://github.com/pingcap/tidb-operator/pull/2894), [@lichunzhu](https://github.com/lichunzhu)) +- Support scaling and auto-failover even if a TiKV store fails in upgrading ([#2886](https://github.com/pingcap/tidb-operator/pull/2886), [@cofyc](https://github.com/cofyc)) +- Fix a bug that the `TidbMonitor` resource could not be set ([#2878](https://github.com/pingcap/tidb-operator/pull/2878), [@weekface](https://github.com/weekface)) +- Fix an error for the monitor creation in the tidb-cluster chart ([#2869](https://github.com/pingcap/tidb-operator/pull/2869), [@8398a7](https://github.com/8398a7)) +- Remove `readyToScaleThresholdSeconds` in `TidbClusterAutoScaler`; TiDB Operator won't support de-noise in `TidbClusterAutoScaler` ([#2862](https://github.com/pingcap/tidb-operator/pull/2862), [@Yisaer](https://github.com/Yisaer)) +- Update the version of TiDB Lightning used in tidb-backup-manager from v3.0.15 to v4.0.2 ([#2865](https://github.com/pingcap/tidb-operator/pull/2865), [@lichunzhu](https://github.com/lichunzhu)) + + # TiDB Operator v1.1.2 Release Notes ## Action Required diff --git a/charts/tidb-cluster/values.yaml b/charts/tidb-cluster/values.yaml index 40e226df2b..50ab71df02 100644 --- a/charts/tidb-cluster/values.yaml +++ b/charts/tidb-cluster/values.yaml @@ -38,7 +38,7 @@ services: type: ClusterIP discovery: - image: pingcap/tidb-operator:v1.1.2 + image: pingcap/tidb-operator:v1.1.3 imagePullPolicy: IfNotPresent resources: limits: diff --git a/charts/tidb-operator/values.yaml b/charts/tidb-operator/values.yaml index d3f160902b..cffb362836 100644 --- a/charts/tidb-operator/values.yaml +++ b/charts/tidb-operator/values.yaml @@ -12,12 +12,12 @@ rbac: timezone: UTC # operatorImage is TiDB Operator image -operatorImage: pingcap/tidb-operator:v1.1.2 +operatorImage: pingcap/tidb-operator:v1.1.3 imagePullPolicy: IfNotPresent # imagePullSecrets: [] # tidbBackupManagerImage is tidb backup manager image -tidbBackupManagerImage: pingcap/tidb-backup-manager:v1.1.2 +tidbBackupManagerImage: pingcap/tidb-backup-manager:v1.1.3 # # Enable or disable tidb-operator features: diff --git a/deploy/aliyun/variables.tf b/deploy/aliyun/variables.tf index 929eb6519e..001de4f7bd 100644 --- a/deploy/aliyun/variables.tf +++ b/deploy/aliyun/variables.tf @@ -10,7 +10,7 @@ variable "bastion_cpu_core_count" { variable "operator_version" { type = string - default = "v1.1.2" + default = "v1.1.3" } variable "operator_helm_values" { diff --git a/deploy/aws/variables.tf b/deploy/aws/variables.tf index 3630029fb4..614f0521b9 100644 --- a/deploy/aws/variables.tf +++ b/deploy/aws/variables.tf @@ -19,7 +19,7 @@ variable "eks_version" { variable "operator_version" { description = "TiDB operator version" - default = "v1.1.2" + default = "v1.1.3" } variable "operator_values" { diff --git a/deploy/gcp/variables.tf b/deploy/gcp/variables.tf index cfb398225c..a471395b0e 100644 --- a/deploy/gcp/variables.tf +++ b/deploy/gcp/variables.tf @@ -28,7 +28,7 @@ variable "tidb_version" { } variable "tidb_operator_version" { - default = "v1.1.2" + default = "v1.1.3" } variable "tidb_operator_chart_version" {