custom resource definition(CRD) ü custom controller Operator 是什么 • Kubernetes 中一切都可视为资源 • 默认资源类型：如 Pod、Service、Volume 等 • Kubernetes 1.7 之后增加了 CRD 自定义资源 • 二次开发扩展 Kubernetes API CRD 的基本原理 ① 观察资源的当前状态 mysql pod-5 mysql pod-6 … … mysql pod-M Node1 kubelet kube-proxy docker mysql pod-0 mysql pod-1 … … mysql pod-N NodeN Mysql Operator pod … … mysql Pod-T 0. 创建 CRD 3. 集群管理 2. 调度 pod Ceph Reflector DeltaFIFO Local Storage Callbacks OnAdd OnUpdate OnDelete WorkQueue List/Watch - CRD - Pod Write Informer Worker ReadOnly • Informer：监听事件并触发回调函数的二级缓存工具包 • WorkQueue：事件合并、过滤、延时、限速 Operator

ion.html What are we solving? Architecture: K8s app using Redis over TLS only app-1 Namespace ms-1 K8s Pod External DB ms-2 K8s Pod ms-3 K8s Pod TLS only ● App with multiple microservices ● into Redis traffic Istio TLS Origination Architecture: K8s app using Redis over TLS only (TLS origination) app-1 Namespace ms-1 K8s Pod External DB container app container istio-proxy TCP TLS

............................................................................ 4 2. PIECLOUDDB 和 K8S 一起部署方案 ........................................................................................... .................................................................................... 10 2.9 安装 K8S 集群 ............................................................................................... ............................................................................... 14 3. PDB 基于已有 K8S 的部署方案 ............................................................................................

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

RESTARTS AGE pod/commerce -apply-schema-initial -vlc6k 0/1 Completed 0 2m42s pod/commerce -apply-vschema -initial -9wb2k 0/1 Completed 0 2m42s pod/vtctld -58bd955948 -pgz7k 1/1 Running 0 2m43s pod/vtgate Running 3 2m43s pod/zone1-commerce -0-init-shard-master-gshz9 0/1 Completed 0 2m42s pod/zone1-commerce -0-replica -0 2/2 Running 0 2m42s pod/zone1-commerce -0-replica -1 2/2 Running 0 2m42s pod/zone1-commerce warning >}} The port-forward will only forward to a specific pod. Currently, kubectl does not automatically terminate a port-forward as the pod dissapears due to apply/upgrade operations. You will need to

RESTARTS AGE pod/commerce -apply-schema-initial -vlc6k 0/1 Completed 0 2m42s pod/commerce -apply-vschema -initial -9wb2k 0/1 Completed 0 2m42s pod/vtctld -58bd955948 -pgz7k 1/1 Running 0 2m43s pod/vtgate Running 3 2m43s pod/zone1-commerce -0-init-shard-master-gshz9 0/1 Completed 0 2m42s pod/zone1-commerce -0-replica -0 2/2 Running 0 2m42s pod/zone1-commerce -0-replica -1 2/2 Running 0 2m42s pod/zone1-commerce warning >}} The port-forward will only forward to a specific pod. Currently, kubectl does not automatically terminate a port-forward as the pod dissapears due to apply/upgrade operations. You will need to

RESTARTS AGE pod/commerce -apply-schema-initial -vlc6k 0/1 Completed 0 2m42s pod/commerce -apply-vschema -initial -9wb2k 0/1 Completed 0 2m42s pod/vtctld -58bd955948 -pgz7k 1/1 Running 0 2m43s pod/vtgate Running 3 2m43s pod/zone1-commerce -0-init-shard-master-gshz9 0/1 Completed 0 2m42s pod/zone1-commerce -0-replica -0 2/2 Running 0 2m42s pod/zone1-commerce -0-replica -1 2/2 Running 0 2m42s pod/zone1-commerce warning >}} The port-forward will only forward to a specific pod. Currently, kubectl does not automatically terminate a port-forward as the pod disappears due to apply/upgrade operations. You will need to

RESTARTS AGE pod/commerce -apply-schema-initial -vlc6k 0/1 Completed 0 2m42s pod/commerce -apply-vschema -initial -9wb2k 0/1 Completed 0 2m42s pod/vtctld -58bd955948 -pgz7k 1/1 Running 0 2m43s pod/vtgate Running 3 2m43s pod/zone1-commerce -0-init-shard-master-gshz9 0/1 Completed 0 2m42s pod/zone1-commerce -0-replica -0 2/2 Running 0 2m42s pod/zone1-commerce -0-replica -1 2/2 Running 0 2m42s pod/zone1-commerce warning >}} The port-forward will only forward to a specific pod. Currently, kubectl does not automatically terminate a port-forward as the pod disappears due to apply/upgrade operations. You will need to

warning >}} The port-forward will only forward to a specific pod. Currently, kubectl does not automatically terminate a port-forward as the pod disappears due to apply/upgrade operations. You will need to these as part of your normal vttablet initialization parameters (e.g. if you are using the Vitess K8s operator): • -init_keyspace restoreks - here restoreks is the recovery keyspace name which we created down by Kubernetes, which also takes care of the use case of a software rollout. If a container or pod is brought down abruptly or crashes, then the primary will be unavailable until Kubernetes restarts

Kubernetes 计算资源 Pod ● Pod ○ 计算任务 → 容器 → Pod ○ 资源分配：CPU，内存，磁盘 ○ 资源调度：Pod → Node ● Pod管理 ○ 无状态计算资源组：Deployment ○ 有状态计算资源组：StatefulSet ● Pod持久存储 ○ 通过PVC申请PV存储资源 ● StatefulSet ○ Pod网络地址不变 ○ Pod与PV映射关系不变 Kubernetes Network Interconnect Standby Pod Master Pod Segment Pod Segment Instance Segment Pod Segment Instance Segment Pod Segment Instance Segment Pod Segment Instance Master StatefulSet (2) Segment节点示例 Greenplum on Kubernetes Greenplum on Kubernetes ● 存储计算分离 ○ PV持久化存储资源 ○ StatefulSet/Pod弹性扩展计算资源 ● 数据库服务层 ○ Service统一Master & Standby Master地址 ● 服务发现机制 ○ 所有节点地址名不变 ● 跨云能力 ○ 容器应用对基础设施透明