Chenggang Shan

Thanks. I 'll look into it.

i have looked up some issues: [https://github.com/kubeedge/kubeedge/issues/3489](url) , [https://github.com/kubeedge/kubeedge/pull/2808](url). It seems like that it has been solved in new version of Kubeedge. Subsequently, i try to install the latest KubeEdge...

Next, I tested Kubeedge V1.9.4, deployed Edgemesh, and found that edgemesh server and edgemesh agent worked fine. > K8s master(192.168.0.160), nodes(192.168.0.161-162), edges(163 raspberry-arm32, 164 raspberry-arm64)  Meanwhile, new problems have...

type 'docker logs 330a76652689' on edge node(192.168.0.164) and show edgemesh-agent logs as follows.   Invoke the Service task-svc-1 by cluster ip (10.68.114.62:6060) in workflow-0-task-0 on 192.168.0.161 and show logs...

The log above is obtained after the edgecore metaServer config is enabled. In other words, the edgecore metaServer startup is not working. 

Does the Kubeedge edge node combined with Edgemesh support gRPC communication? My application in pod `workflow-0-task-1` on the edge needs to build the GRPC server. The code is as follows....

@Poorunga

@Poorunga Does edgemesh agent support gRPC communication between cloud pods and edge pods?

i have verified the test instance supported by the official documentation. [https://edgemesh.netlify.app/guide/test-case.html#prepare](url). Edgemesh can support gRPC communication between cloud pods and edge pods. The reason for the above issue is...

Then I encountered a new problem. I need to finish grpc communication between K8s node's pods and edge pods via Service and edge pods fail to obtain Service env. Under...