TiDB Operator v1.1.0-beta.1

We're glad to announce the v1.1.0-beta.1 release of TiDB Operator.

This is a pre-release of v1.1.0, which focuses on the usability, extensibility and security of TiDB Operator. While we encourage usage in non-critical environments, it is NOT recommended to use this version in critical environments.

Please refer to the changelog for all the changes in this release.

Docker images:

docker pull pingcap/tidb-operator:v1.1.0-beta.1
docker pull uhub.ucloud.cn/pingcap/tidb-operator:v1.1.0-beta.1

Contributors

Our thanks go to the following contributors from the community for helping this release:

• @shonge
• @mikechengwei

TiDB Operator 1.0.6

Action required: Users should migrate the configs in values.yaml of previous chart releases to the new values.yaml of the new chart. Otherwise, the monitor pods might fail when you upgrade the monitor with the new chart.

For example, configs in the old values.yaml file:

monitor:
  ...
  initializer:
    image: pingcap/tidb-monitor-initializer:v3.0.5
    imagePullPolicy: IfNotPresent
  ...
  reloader:
    ...
    image: pingcap/tidb-monitor-reloader:v1.0.0
  ...

After migration, configs in the new values.yaml file should be as follows:

monitor:
  ...
  initializer:
    image: pingcap/tidb-monitor-initializer:v3.0.5
    imagePullPolicy: Always
    config:
      K8S_PROMETHEUS_URL: http://prometheus-k8s.monitoring.svc:9090
  ...
  reloader:
    ...
    image: pingcap/tidb-monitor-reloader:v1.0.1
  ...

For user guide, please check out document.

Docker images:

docker pull pingcap/tidb-operator:v1.0.6
docker pull uhub.ucloud.cn/pingcap/tidb-operator:v1.0.6

Monitor

• Enable alert rule persistence (#898)
• Add node & pod info in TiDB Grafana (#885)

TiDB Scheduler

• Refine scheduler error messages (#1373)

Compatibility

• Fix the compatibility issue in Kubernetes v1.17 (#1241)
• Bind the system:kube-scheduler ClusterRole to the tidb-scheduler service account (#1355)

TiKV Importer

• Fix the default tikv-importer configuration (#1415)

E2E

• Ensure pods unaffected when upgrading (#955)

CI

• Move the release CI script from Jenkins into the tidb-operator repository (#1237)
• Adjust the release CI script for the release-1.0 branch (#1320)

TiDB Operator 1.0.5

For existing TiDB clusters. Upgrading tidb-cluster chart will trigger a rolling update for these pods: pd, tikv, pump and drainer.

Please check out CHANGELOG for a full list of changes. For user guide, please check out document.

Docker images:

docker pull pingcap/tidb-operator:v1.0.5
docker pull uhub.ucloud.cn/pingcap/tidb-operator:v1.0.5

TiDB Operator v1.0.4

We're glad to announce the v1.0.4 release of TiDB Operator!

v1.0.4 is mainly focused on stability and ease of use. This release adds hostNetwork and podSecurityContext support for TiDB cluster, which empowers much fine-grained controls over the behavior of TiDB cluster Pods. Also, new charts tidb-lightning and tidb-drainer are introduced, marking the maturity of support for TiDB ecosystem tools.

Please check out the CHANGELOG for a full list of changes. For user guide, please check out our document.

Note:

The default image version in v1.0.4 helm chart is not updated to v1.0.4, you have to set the operatorImage variable to upgrade your operator to v1.0.4v explicitly.

Docker images:

docker pull pingcap/tidb-operator:v1.0.4
docker pull uhub.ucloud.cn/pingcap/tidb-operator:v1.0.4

Contributors

Our thanks go to the following contributors from the community for helping this release:

• @shonge

Additional Notes for Users of v1.1.0.alpha branch

For historical reasons, v1.1.0.alpha is a hot-fix branch and got this name by mistake. All fixes in that branch are cherry-picked to v1.0.4 and the v1.1.0.alpha branch will be discarded to keep things clear.

We strongly recommend you to upgrade to v1.0.4 if you are using any version under v1.1.0.alpha.

v1.0.4 introduces the following fixes comparing to v1.1.0.alpha.3:

• Support HostNetwork (#1202)
• Add the permit host option for tidb-initializer job (#779)
• Fix drainer misconfiguration in tidb-cluster chart (#945)
• Set the default externalTrafficPolicy to be Local for TiDB services (#960)
• Fix tidb-operator crash when users modify sts upgrade strategy improperly (#969)
• Add the maxFailoverCount limit to TiKV (#976)
• Fix values file customization for tidb-operator on aliyun (#983)
• Do not limit failover count when maxFailoverCount = 0 (#978)
• Suspend the ReplaceUnhealthy process for TiKV auto-scaling-group on AWS (#1027)
• Fix the issue that the create_tidb_cluster_release variable does not work (#1066))
• Add v1 to statefulset apiVersions (#1056)
• Add timezone support (#1126)

TiDB Operator v1.0.3

This release upgrades default TiDB version to v3.0.5 which fixed a serious bug in TiDB. So if you are using TiDB v3.0.4 or prior versions, you must upgrade to v3.0.5.

This release adds the timezone support for all charts.

For existing TiDB clusters. If the timezone in tidb-cluster/values.yaml has been customized to other timezones instead of the default UTC, then upgrading tidb-operator will trigger a rolling update for the related pods.

The related pods include pump, drainer, dicovery, monitor, scheduled backup, tidb-initializer, and tikv-importer.

The time zone for all images maintained by tidb-operator should be UTC. If you use your own images, you need to make sure that the corresponding time zones are UTC.

Please check out CHANGELOG for a full list of changes. For user guide, please check out document.

Docker images:

docker pull pingcap/tidb-operator:v1.0.3
docker pull uhub.ucloud.cn/pingcap/tidb-operator:v1.0.3

TiDB Operator v1.0.2

The AWS Terraform script uses auto-scaling-group for all components (PD/TiKV/TiDB/monitor). When an ec2 instance fails the health check, the instance will be replaced. This is helpful for those applications that are stateless or use EBS volumes to store data.

But a TiKV Pod uses instance store to store its data. When an instance is replaced, all the data on its store will be lost. TiKV has to resync all data to the newly added instance. Though TiDB is a distributed database and can work when a node fails, resyncing data can cost much if the dataset is large. Besides, the ec2 instance may be recovered to a healthy state by rebooting.

So we disabled the auto-scaling-group's replacing behavior in v1.0.2.

Auto-scaling-group scaling process can also be suspended according to its documentation if you are using v1.0.1 or prior versions.

Please check out CHANGELOG for a full list of changes. For user guide, please check out document.

Docker images:

docker pull pingcap/tidb-operator:v1.0.2
docker pull uhub.ucloud.cn/pingcap/tidb-operator:v1.0.2

v1.1.0-alpha.3

• Support specifying SecurityContext for PD, TiKV and TiDB Pods and enable tcp keepalive for AWS. #915
• Add zone label and reserved resources arguments to kubelet #871

Upgrade Process

Upgrading the operator won't affect the cluster.

Upgrading the Terraform script (and apply the upgraded version) won't affect the existing nodes, but the configuration of tidb-servers will be changed. Therefore, a rolling-update of tidb-servers will be triggered.

If you want to enable server-side tcp keepalive on an existing cluster, you have to manually release the EC2 instances in which the tidb-servers running to get them re-created using the new tcp_keepalived configuration.

TiDB Operator v1.0.1

This release fixes some serious bugs:

• We fixed a serious bug (#878) that may cause all PD and TiKV pods to be accidentally deleted when kube-apiserver fails. But the data is safe. This would cause TiDB service outage. So if you are using v1.0.0 or prior versions, you must upgrade to v1.0.1.
• The backup tool image pingcap/tidb-cloud-backup uses a forked version of Mydumper. The current version pingcap/tidb-cloud-backup:20190610 contains a serious bug that could result in a missing column in the exported data. This is fixed in #29. And the default image used now contains this fixed version. So if you are using the old version image for backup, you must upgrade to use pingcap/tidb-cloud-backup:201908028 and do a new full backup to avoid potential data inconsistency.

Please check out CHANGELOG for a full list of changes. For user guide, please check out document.

Docker images:

docker pull pingcap/tidb-operator:v1.0.1
docker pull uhub.ucloud.cn/pingcap/tidb-operator:v1.0.1

v1.1.0-alpha.2

fix some orphan pods cleaner bugs #878

v1.1.0-alpha.0

add tikvGCLifeTime option (#835)