Ryan

the working plan of DMI in 2023 has been proposed in #4744 . welcome to join us.

Hello @wackxu , this PR may not resolve the problem in https://github.com/kubeedge/kubeedge/issues/3445. The problem still exists when user uses edgemesh for DNS resolving.

/lgtm

> 是的，KubeEdge目前这套方式不太适合大量数据采集场景，数据量过大会占用云边websocket通道，K8s的大量写操作也可能把ETCD冲挂。我们目前在搞一套新的KubeEdge设备管理方案DMI，在考虑使用单独做个通道来传输本地数据，方案相关如下链接，欢迎多提意见。 https://github.com/kubeedge/kubeedge/issues/3760

> > > > > > > > > 是的，KubeEdge目前这套方式不太适合大量数据采集场景，数据量过大会占用云边websocket通道，K8s的大量写操作也可能把ETCD冲挂。我们目前在搞一套新的KubeEdge设备管理方案DMI，在考虑使用单独做个通道来传输本地数据，方案相关如下链接，欢迎多提意见。 #3760 > > 单独做通道来传IoT数据只是解决通道隔离的问题，并没有解决大量写操作etcd的问题吧，如果没有改变用etcd来管理设备的现状态，始终会面临该问题。 嗯新方案里不会把采集的数据保存到etcd里，而是在边缘侧按需分发，比如缓存本地数据库，推送到云或边的指定APP，被数据应用主动GET查询等，kubeedge及etcd只保存设备管理相关信息以及配置类数据，可以大大降低etcd的负载

ok, i will update the meeting info about the sig device-iot

> Register a GitHub Account and check the [repository](https://github.com/kubeedge/kubeedge) and [document](https://kubeedge.io/) of KubeEdge]. done and stared > > fix a typo of doc: [kubeedge/website#274](https://github.com/kubeedge/website/pull/274) > > add a ut for...

The link of Course Certification is: https://shimo.im/forms/SrAsA6Wemuk0a4w6/fill The link of Final Exam is: https://github.com/kubeedge/community/issues/138 The link of Application Form is: https://shimo.im/forms/5bqnr5VRV6fL98qy/fill

The tasks for Class 4 of the Course has been released in https://github.com/kubeedge/community/issues/119

The tasks for Class 6 of the Course has been released in https://github.com/kubeedge/community/issues/120