Kubeedge's core philosophy

The core idea

• Cloud side collaboration
  • Bidirectional multiplexing message channel , Support edge node in private network ( The edge network does not need a public network Ip, You only need to have the ability to access the public network , Support for home networking , LAN, etc )
  • Websocket+ Message encapsulation , Dramatically reduce communication pressure , It can still work under high time delay
• Edge offline autonomy
  • Node metadata persistence , Implement node level offline autonomy
  • Node failure recovery does not require List-watch, Reduce network stress , Fast ready ( Native k8s After the failure , Need to look like master Total quantity list To restore )
• Extremely lightweight
  • restructuring Kubelet Function module , Ultra lightweight （~10mb Memory footprint ）
  • Remove the embedded storage driver , adopt CSI Access
  • Support CRI Integrate Containerd、CRI-O, Optimize runtime resource consumption

Detailed introduction :

• Cloud side collaboration Cloud side collaboration is KubeEdge A highlight of .KubeEdge adopt Kubernetes standard API Managing edge nodes in the cloud 、 Add, delete, modify and check the equipment and workload . System upgrades and application updates of edge nodes can be directly distributed from the cloud , Improve the operation and maintenance efficiency of the edge . in addition ,KubeEdge The bottom optimized multiplex message channel is relative to Kubernetes be based on HTTP Long connection list/watch The mechanism is more extensible , Allow access to a large number of edge nodes and devices .KubeEdge Cloud components are completely open source , Users can be in any public cloud / Deploy on private cloud KubeEdge And don't worry about vendor lock-in , And freely integrate other services of the public cloud .
• Edge node offline autonomy And Kubernetes The nodes of the cluster are different , Edge nodes need to work autonomously in a completely disconnected mode , There is no periodic state synchronization , Only when reconnecting will it communicate with the control surface . This mode is consistent with Kubernetes The management surface and work nodes are connected by heartbeat and list/watch The original design that keeps the status updated is very different . KubeEdge The off-line autonomy of nodes is realized by message bus and local storage of metadata . The control plane configuration and device real-time status updates expected by users are synchronized to local storage through messages , In this way, the node will not lose the management metadata even if it is restarted offline , And maintain the management ability of the node equipment and application .
• Equipment management KubeEdge It provides a pluggable unified device management framework , It allows users to develop device access drivers according to different protocols or actual needs on this framework . Currently, the agreements supported and planned to support are ：MQTT,BlueTooth,OPC UA,Modbus etc. , As more and more community partners join ,KubeEdge More device communication protocols will be supported in the future .KubeEdge adopt device twins/digital twins Update and synchronize equipment status , And provide... In the cloud Kubernetes An extension of API Abstract device objects , Users can use... In the cloud kubectl operation Kubernetes Manage edge devices as resource objects .
• Lightweight In order to Kubernetes Deploy on edge ,KubeEdge A lightweight transformation has been carried out .KubeEdge Retain the Kubernetes The management of , Redeveloped lightweight nodes agent.

 

all 1202 Years. , Do not know edge computing and edge computing platform kubeedge Do you - Listen to the wind chanting articles - You know https://zhuanlan.zhihu.com/p/342626632