StatefulSet を使って tidb や tikv のコンポー ネントを作成します StatefulSet は Pod を指定された数だけシーケンシャルに作成します (mypod-0, mypod-1 ,,, mypod-N) Pod が増える時は Pod の名前の末尾の数字が増えていき、Pod が減る時 は末尾の数字が大きいものから減っていきます Open Source Conference StatefulSet を使う つまり、通常の StatefulSet だとこういう状態にすることはできません mypod-0 mypod-4 mypod-2 mypod-3 特定の番号の Pod (今回の例だと 1 ) だけ欠番にして通常通り運用したい・・・ そんな願いを叶えてくれるのが Advanced StatefulSet になります ... Open Source Conference Open Source Conference 2022 Online/Spring 58 Advanced StatefulSet を使う Advanced StatefulSet は消したい Pod を annotation で記述します mypod-0 mypod-1 mypod-2 mypod-3 mypod-0 mypod-1 mypod-2 mypod-3 mypod-1 を消したい！

com - Kubernetes has pod, deployment, statefulset, etc. - But it does not know how to operate a TiDB cluster... Kubernetes Pattern - Declarative Model PingCAP.com - Kubernetes has pod, deployment, statefulset PingCAP.com Scheduler Extender kube-scheduler kube-scheduler tidb-scheduler other Pod other Pod other Pod PD Pod TiKV Pod TiDB Pod PingCAP.com Scheduler Extender 3 TiKV ❌ Node-A Node-B Node-C TiKV TiKV

做了调度策略的增强,实现 TiDB 集群的各个 Pod 在多机房之间的打散和调度, 提升了 业务的云上容灾能力。 新架构使得运维管控层变薄, 大部分的运维功能下沉到 Operator 来实现, DBA 日常操作的运维工作让 RD 自助进行TiDB 集群的管理变得容易, 且自动容错能力非常强, 遇到 TiKV 或者 PD 节点宕机, K8S 集群自动 扩容出新的 Pod 来接蔡, 不需要 DBA 手动干预,节省大量运维成本。

on Kubernetes as an independent Pod #1447 @SabaPing TiDB v6.5.0 (and later) and TiDB Operator v1.4.0 (and later) support deploying TiDB Dashboard as an independent Pod on Kubernetes. Using TiDB Operator Operator, you can access the IP address of this Pod to start TiDB Dashboard. Independently deploying TiDB Dashboard provides the following benefits: • The compute work of TiDB Dashboard does not pose pressure pvc ${pvc_name} --wait=false 2. Delete the TiKV Pod and wait for newly created TiKV Pods to join the cluster. kubectl delete -n ${namespace} pod ${pod_name} 8.11 Replicate Data Between Primary and Secondary

TiDB Dashboard 在 Kubernetes 环境支持独立 Pod 部署 #1447 @SabaPing TiDB v6.5.0 且 TiDB Operator v1.4.0 之后，在 Kubernetes 上支持将 TiDB Dashboard 作为独立的 Pod 部署。在 TiDB Operator 环境，可直接访问该 Pod 的 IP 来打开 TiDB Dashboard。 独立部署 kubectl delete -n ${namespace} pvc ${pvc_name} --wait=false 2. 删除 TiKV Pod，并等待新创建的 TiKV Pod 加入集群。 kubectl delete -n ${namespace} pod ${pod_name} 8.11 搭建双集群主从复制 本文档介绍如何配置一个 TiDB 集群以及该集群的 TiDB 或 MySQL 从集群，并将增量数据实时从主集群同步到从 PD 组件中，无需独立部署。 注意： TiDB v6.5.0 且 TiDB Operator v1.4.0 之后，在 Kubernetes 上支持将 TiDB Dashboard 作为独立的 Pod 部 署。具体信息，参考 TiDB Operator 部署独立的 TiDB Dashboard。 图 489: 界面 TiDB Dashboard 在 GitHub 上开源。 以下列出了 TiDB

pvc ${pvc_name} --wait=false 2. Delete the TiKV Pod and wait for newly created TiKV Pods to join the cluster. kubectl delete -n ${namespace} pod ${pod_name} 8.12 Replicate Data Between Primary and Secondary optimize the cluster behavior: • TiDB: Takes the TiDB node offline by cordoning it and deleting the TiDB pod. This assumes that the node pool of the TiDB instance is set to auto-scale and dedicated to TiDB. Other (and later) and TiDB Operator v1.4.0 (and later) support de- ploying TiDB Dashboard as an independent Pod on Kubernetes. For details, see Deploy TiDB Dashboard independently in TiDB Operator. 4426 Figure

pvc ${pvc_name} --wait=false 2. Delete the TiKV Pod and wait for newly created TiKV Pods to join the cluster. kubectl delete -n ${namespace} pod ${pod_name} 8.12 Replicate Data Between Primary and Secondary optimize the cluster behavior: • TiDB: Takes the TiDB node offline by cordoning it and deleting the TiDB pod. This assumes that the node pool of the TiDB instance is set to auto-scale and dedicated to TiDB. Other (and later) and TiDB Operator v1.4.0 (and later) support de- ploying TiDB Dashboard as an independent Pod on Kubernetes. For details, see Deploy TiDB Dashboard independently in TiDB Operator. Figure 558:

pvc ${pvc_name} --wait=false 2. Delete the TiKV Pod and wait for newly created TiKV Pods to join the cluster. kubectl delete -n ${namespace} pod ${pod_name} 8.12 Replicate Data Between Primary and Secondary optimize the cluster behavior: • TiDB: Takes the TiDB node offline by cordoning it and deleting the TiDB pod. This assumes that the node pool of the TiDB instance is set to auto-scale and dedicated to TiDB. Other (and later) and TiDB Operator v1.4.0 (and later) support de- ploying TiDB Dashboard as an independent Pod on Kubernetes. For details, see Deploy TiDB Dashboard independently in TiDB Operator. Figure 525:

kubectl delete -n ${namespace} pvc ${pvc_name} --wait=false 2. 删除 TiKV Pod，并等待新创建的 TiKV Pod 加入集群。 kubectl delete -n ${namespace} pod ${pod_name} 8.12 搭建双集群主从复制 本文档介绍如何配置一个 TiDB 集群以及该集群的 TiDB 或 MySQL 从集群，并将增量数据实时从主集群同步到从 PD 组件中，无需独立部署。 注意： TiDB v6.5.0 且 TiDB Operator v1.4.0 之后，在 Kubernetes 上支持将 TiDB Dashboard 作为独立的 Pod 部 署。具体信息，参考 TiDB Operator 部署独立的 TiDB Dashboard。 3491 图 507: 界面 TiDB Dashboard 在 GitHub 上开源。 以下列出了 Dashboard 就会原生集成。 注意： TiDB v6.5.0 且 TiDB Operator v1.4.0 之后，在 Kubernetes 上支持将 TiDB Dashboard 作为独立的 Pod 部 署。具体信息，参考 TiDB Operator 部署独立的 TiDB Dashboard。 3493 请参阅下列文档了解如何部署标准 TiDB 集群： • 快速试用 TiDB 集群 •

pvc ${pvc_name} --wait=false 2. Delete the TiKV Pod and wait for newly created TiKV Pods to join the cluster. kubectl delete -n ${namespace} pod ${pod_name} 8.12 Replicate Data Between Primary and Secondary optimize the cluster behavior: • TiDB: Takes the TiDB node offline by cordoning it and deleting the TiDB pod. This assumes that the node pool of the TiDB instance is set to auto-scale and dedicated to TiDB. Other (and later) and TiDB Operator v1.4.0 (and later) support de- ploying TiDB Dashboard as an independent Pod on Kubernetes. For details, see Deploy TiDB Dashboard independently in TiDB Operator. 4780 Figure