Jiezhang Wang

+1 ``` // AverageLoad exposes the current average load. func (c *Consistent) AverageLoad() float64 { avgLoad := float64(c.partitionCount/uint64(len(c.members))) * c.config.Load return math.Ceil(avgLoad) } ``` len(c.members) may be equal to zero

@vcozzolino Seems to be using a different version of edgemesh-agent. You can checkout every edgemesh-agent image ID.

1. checkout edgecore.yaml, need set clusterDNS and clusterDomain, metaServer need enable: true, refer to: https://edgemesh.netlify.app/guide/getting-started.html#manual-installation 2. test local apiserver in edge node, like: curl 127.0.0.1:10550/api/v1/services 3. print some edgemesh-agent logs...

Try deploy other test pod to edge node? such as nginx image

Try `kubectl apply -f https://github.com/kubeedge/kubeedge/raw/master/build/deployment.yaml`, then observe that nginx can run normally on the edge node? **You need to make sure your kubeedge cluster is normal first, kubeedge itself has...

> I can't deploy it on the edge node, because I don't deploy flannel and kube-proxy on the edge. You can run pods on your edge nodes without kube-proxy and...

Maybe a kubeedge bug, see issue: https://github.com/kubeedge/kubeedge/issues/3489

> > @skrlin @JoeyHwong-gk It is very hard to understand why your image is produced `2 months ago`. Did you make sure that you have successfully updated the image? >...

Currently, you can only keep the EDGE-MESH chain in front of KUBE-SERVICES by deleting the EDGE-MESH chain and then recreating the edgemesh. ``` $ iptables -t nat -D OUTPUT 3...

When the KUBE-SERVICES chain exists, kube-proxy will not rebuild the KUBE-SERVICES chain. Rebuilding the KUBE-SERVICES chain will insert the first place in the system root chain (such as OUTPUT, PREROUTING)....