Release date: December 27, 2019
TiDB Operator version: 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
monitor: ... initializer: image: pingcap/tidb-monitor-initializer:v3.0.5 imagePullPolicy: IfNotPresent ...
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 ...
- Refine scheduler error messages (#1373)
- Fix the compatibility issue in Kubernetes v1.17 (#1241)
- Bind the
system:kube-schedulerClusterRole to the
tidb-schedulerservice account (#1355)
- Fix the default
- Ensure pods unaffected when upgrading (#955)