TiDB Operator 1.0 GA Release Notes

    TiDB Operator version: 1.0.0

    • ACTION REQUIRED: was removed from values.yaml. You can directly set it with location-labels in pd.config.
    • ACTION REQUIRED: the --features flag of tidb-scheduler has been updated to the key={true,false} format. You can enable the feature by appending =true.
    • ACTION REQUIRED: you need to change the configurations in values.yaml of previous chart releases to the new values.yaml of the new chart. Otherwise, the configurations will be ignored when upgrading the TiDB cluster with the new chart.

    The pd section in old values.yaml:

    1. pd:
    2.   config: |
    3.     [log]
    4.     level = "info"
    5.     [schedule]
    6.     max-store-down-time = "30m"
    7.     [replication]
    8.     max-replicas = 3

    The tikv section in old values.yaml:

    The tikv section in new values.yaml:

    1. tikv:
    2.   config: |
    3.     log-level = "info"
    4.     [server]
    6.     [raftstore]
    7.     sync-log = true
    8.     [readpool.storage]
    9.     high-concurrency = 4
    10.     normal-concurrency = 4
    11.     low-concurrency = 4
    12.     [readpool.coprocessor]
    13.     high-concurrency = 8
    14.     normal-concurrency = 8
    15.     low-concurrency = 8
    16.     scheduler-worker-pool-size = 4

    The tidb section in new values.yaml:

    1. tidb:
    2.   config: |
    3.     token-limit = 1000
    4.     mem-quota-query = 34359738368
    5.     check-mb4-value-in-utf8 = true
    6.     treat-old-version-utf8-as-utf8mb4 = true
    7.     lease = "45s"
    8.     [log]
    9.     level = "info"
    10.     [prepared-plan-cache]
    11.     enabled = false
    12.     capacity = 100
    14.     enabled = false
    15.     capacity = 10240000
    16.     [performance]
    17.     txn-entry-count-limit = 300000
    18.     txn-total-size-limit = 104857600
    19.     max-procs = 0

    The monitor section in old values.yaml:

    1. monitor:
    2.   create: true
    3.    initializer:
    4.      image: pingcap/tidb-monitor-initializer:v3.0.5
    5.      imagePullPolicy: IfNotPresent
    6.    reloader:
    7.      create: true
    8.      image: pingcap/tidb-monitor-reloader:v1.0.0
    9.      imagePullPolicy: IfNotPresent
    10.      service:
    11.        type: NodePort
    12.   ...

    Please check cluster configuration for detailed configuration.

    • Simplify GKE SSD setup
    • Modularization for AWS Terraform scripts
    • Turn on the automatic failover feature by default
    • Enable configmap rollout by default
    • Enable stable scheduling by default
    • Support multiple TiDB clusters management in Alibaba Cloud
    • Enable AWS NLB cross zone load balancing by default
    • Fix sysbench installation on bastion machine of AWS deployment
    • Fix TiKV metrics monitoring in default setup

    Detailed Bug Fixes and Changes

    • Allow upgrading TiDB monitor along with TiDB version (#666)
    • Specify the TiKV status address to fix monitoring ()
    • Fix sysbench installation on bastion machine for AWS deployment (#688)
    • Update the git add upstream command to use https in contributing document ()
    • Stability cases: stop kubelet and etcd (#665)
    • Limit test cover packages ()
    • Enable nlb cross zone load balancing by default (#686)
    • Add TiKV raftstore parameters ()
    • Support multiple TiDB clusters management for Alibaba Cloud (#658)
    • Adjust the EndEvictLeader function ()
    • Add more logs (#676)
    • Update feature gates to support key={true,false} syntax ()
    • Fix the typo meke to make (#679)
    • Enable configmap rollout by default and quote configmap digest suffix ()
    • Turn automatic failover on (#667)
    • Sets node count for default pool equal to total desired node count ()
    • Upgrade default TiDB version to v3.0.1 (#671)
    • Remove storeLabels ()
    • Change the way to configure TiDB/TiKV/PD in charts (#638)
    • Modularize for AWS terraform scripts ()
    • Change the DeferClose function (#653)
    • Increase the default storage size for Pump from 10Gi to 20Gi in response to stop-write-at-available-space ()
    • Simplify local SDD setup (#644)