- 关于 TiDB Operator
- 快速上手
- 部署
- 自托管的 Kubernetes
- 公有云的 Kubernetes
- 在 ARM64 机器上部署 TiDB 集群
- 部署 TiDB HTAP 存储引擎 TiFlash
- 跨多个 Kubernetes 集群部署 TiDB 集群
- 部署 TiDB 异构集群
- 部署增量数据同步工具 TiCDC
- 部署 Binlog 收集工具
- 监控与告警
- 数据迁移
- 运维管理
- 安全
- 扩缩容
- 升级
- 升级 TiDB 集群
- 升级 TiDB Operator
- 备份与恢复
- 备份与恢复简介
- 备份与恢复 CR 介绍
- 远程存储访问授权
- 使用 Amazon S3 兼容的存储
- 使用 Google Cloud Storage
- 使用持久卷
- 运维
- 灾难恢复
- 故障诊断
- 常见问题
- 参考
- 版本发布历史
- v1.3
- v1.2
- v1.1
- v1.0
- v0
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:
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
...
Monitor
TiDB Scheduler
- Refine scheduler error messages (#1373)
Compatibility
- Fix the compatibility issue in Kubernetes v1.17 (#1241)
- Bind the
system:kube-scheduler
ClusterRole to thetidb-scheduler
service account (#1355)
TiKV Importer
- Fix the default
tikv-importer
configuration (#1415)
E2E
- Ensure pods unaffected when upgrading (#955)
CI
文档内容是否有帮助?