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
the core concept is: the cloud side stuff , operator, will generate/maintain all the necessary configuration in a configmap for each edge node. the edge side staff, agent, will consume it, then do the necessary work, such as to establish the tunnels. We depends on the functionality of kubeedge: to pass the configmap from cloud to edge. That is all.
What kubeedge feature does fabedge depend on, such as Autonomic Kube-API Endpoint for list-watch, kubectl exec on the edge or others?
The text was updated successfully, but these errors were encountered: