You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cloud-edge collaboration scenario, the edge is connected to the cloud through the public network, and the edge nodes may be disconnected from the cloud due to various objective or subjective factors. The update of Workloads (Deployment, DaemonSet, etc.) in the native Kubernetes relies on the connectivity of the edge nodes to the cloud network. Therefore, when the cloud-edge network is disconnected, workloads cannot be successfully updated, we need to explore a suitable way to update the application.
Describe your problem
In cloud-edge collaboration scenario, the edge is connected to the cloud through the public network, and the edge nodes may be disconnected from the cloud due to various objective or subjective factors. The update of Workloads (Deployment, DaemonSet, etc.) in the native Kubernetes relies on the connectivity of the edge nodes to the cloud network. Therefore, when the cloud-edge network is disconnected, workloads cannot be successfully updated, we need to explore a suitable way to update the application.
在云边协同场景下,边缘与云端通过公网连接(例如WIFI,4G,5G等),由于各种客观或主观因素,边缘节点可能与云端断开网络连接。而原生Kubernetes中的Workload(如Deployment,DaemonSet等)的升级都依赖边缘节点与云端网络连通。因此当云边网络断连状态下,如何完成边缘业务的升级成为云边协同场景下一个非常值得探索的课题。
This issue is part of summer-ospp
Mentor: Bingchang Tang
The text was updated successfully, but these errors were encountered: