You are viewing the documentation for an older major version of the TiDB Operator tool (TiDB Operator v1.0).

TiDB Operator release-1.3, the latest major version of TiDB Operator, is now stable and recommended for general use. To view this page for TiDB Operator release-1.3, click here.

TiDB Operator 1.0.6 Release Notes

Release date: December 27, 2019

TiDB Operator version: 1.0.6

v1.0.6 What's New

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:

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

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

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


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

TiDB Scheduler

  • Refine scheduler error messages (#1373)


  • 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)


  • Ensure pods unaffected when upgrading (#955)


  • 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)
Was this page helpful?