关于集群端组件轻量化的需求

[poneding]

关于集群端组件轻量化的需求

• 对接云边端轻量化的集群时，region 端组件显得就不那么轻量化了；
• 部署的组件较多，容易带来部署问题；
• 版本开发完成后编译发布组件比较复杂；
• 组件调用，消息队列机制导致开发调试困难；

轻量化建议

在Region端不使用 etcd，db存储，不使用 mq 机制

• 将数据定义成 CRD；
• 使用 client-go 自带的 queue 机制；
• chaos 改为实时任务（有编译任务时启动 pod 完成相应任务，完成后就回收）；
• 利用 Operator + RegionApi 来完成绝大多数集群端工作；
• 其他待发掘...

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Requirements for lightweight cluster-side components

• When connecting to the cloud-side lightweight cluster, the region-side components are not so lightweight;
• There are many components deployed, which is easy to bring deployment problems;
• It is more complicated to compile and publish components after version development is completed;
• Component calls and message queue mechanism make development and debugging difficult;

Lightweight suggestion

Do not use etcd, db storage, and do not use mq mechanism on the Region side

• Define data as CRD;
• Use the queue mechanism that comes with client-go;
• chaos is changed to a real-time task (when there is a compilation task, start the pod to complete the corresponding task, and then recycle it after completion);
• Use Operator + RegionApi to complete most of the cluster-side work;
• Others to be discovered...