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
Related Pr submissions, supplementary unit testing, and e2e testing, demonstration demos, and usage documents
Why is this needed:
KubeEdge extends the capabilities of Kubernetes to edge scenarios, providing infrastructure support for networking, application deployment, and metadata synchronization between the cloud and the edge. In an edge scenario, the edge node may be in a private network and cannot be accessed from the cloud. Therefore, it is necessary to access the cloud from the edge node and establish a two-way communication link in reverse. Currently, kubeedge only supports single node access. However, in actual business scenarios, there may be a large number of edge nodes. Single access is very troublesome, so batch access nodes need to be supported. What needs to be done: to be done: Support batch access to nodes, which can be achieved with the help of scripts or other methods.
What would you like to be added/modified:
Why is this needed:
KubeEdge extends the capabilities of Kubernetes to edge scenarios, providing infrastructure support for networking, application deployment, and metadata synchronization between the cloud and the edge. In an edge scenario, the edge node may be in a private network and cannot be accessed from the cloud. Therefore, it is necessary to access the cloud from the edge node and establish a two-way communication link in reverse. Currently, kubeedge only supports single node access. However, in actual business scenarios, there may be a large number of edge nodes. Single access is very troublesome, so batch access nodes need to be supported. What needs to be done: to be done: Support batch access to nodes, which can be achieved with the help of scripts or other methods.
Refer:
https://github.com/kubeedge/kubeedge
The text was updated successfully, but these errors were encountered: