kubeedge: Edgecore published service as 127.0.0.1:10350 which cannot be connected with cloud core endpoint

What happened: Edge core service published with port 127.0.0.1:10350 service cannot be visited by cloud core endpoint for K8s flannel service.

root@ubuntu-bionic:~# kubectl get po -n kube-system
NAME                                    READY   STATUS    RESTARTS   AGE
coredns-7f9c544f75-br94t                1/1     Running   0          2m21s
coredns-7f9c544f75-gzm8k                1/1     Running   0          2m21s
etcd-ubuntu-bionic                      1/1     Running   0          2m18s
kube-apiserver-ubuntu-bionic            1/1     Running   0          2m18s
kube-controller-manager-ubuntu-bionic   1/1     Running   0          2m18s
kube-flannel-ds-amd64-zhkzg             1/1     Running   0          118s
kube-flannel-ds-arm64-ngtxj             0/1     Error     0          31s
kube-proxy-5qvbz                        1/1     Running   0          2m22s
kube-scheduler-ubuntu-bionic            1/1     Running   0          2m17s
root@ubuntu-bionic:~# docker logs -f kube-flannel-ds-arm64-ngtxj -n kube-system
unknown shorthand flag: 'n' in -n
See 'docker logs --help'.
root@ubuntu-bionic:~# kubectl logs -f kube-flannel-ds-arm64-ngtxj -n kube-system
Error from server: Get https://10.164.17.79:10350/containerLogs/kube-system/kube-flannel-ds-arm64-ngtxj/kube-flannel?follow=true: dial tcp 10.164.17.79:10350: connect: connection refused

kube-flannel-ds-arm64-ngtxj failed due to it cannot connect endpoint of edgecore service. while at the edgecore this port is published as 127.0.0.1:10350 which cannot be visited outside this host.

root@board-desktop:~# netstat -tunlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 172.17.0.1:40001        0.0.0.0:*               LISTEN      470493/edgecore     
tcp        0      0 127.0.0.1:10350        0.0.0.0:*               LISTEN      470493/edgecore    

What you expected to happen: How could I set to solve this problem when starting edge core service? How to reproduce it (as minimally and precisely as possible): Normally setup K8s cluster with KubeEdge cloud core service and then connect edge core service to this server. Anything else we need to know?:

Environment:

• KubeEdge version(e.g. cloudcore/edgecore --version):
  1.3.1 CloudSide Environment:
• Hardware configuration (e.g. lscpu): 2C
• OS (e.g. cat /etc/os-release): Ubuntu 18.04
• Kernel (e.g. uname -a): Linux ubuntu-bionic 4.15.0-111-generic #112-Ubuntu SMP Thu Jul 9 20:32:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
• Go version (e.g. go version): go version go1.12.16 linux/amd64
• Others:

EdgeSide Environment:

• edgecore version (e.g. edgecore --version):
• Hardware configuration (e.g. lscpu):
• OS (e.g. cat /etc/os-release):
• Kernel (e.g. uname -a):
• Go version (e.g. go version):
• Others: