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)