What happened:
Figure 1

As shown in Figure 1, when creating EdgeApplication, if two same node groups are configured at the same time, the instance deployment will fail and a large number of status information will be reported continuously (as shown in Figure 2), which will lead to the bursting of edgecore's websocket message channel. Which in turn led to edgecore's repeated restarts (as shown in Figure 3).

Temporary solution: Temporary workaround: First delete the created problematic EdgeApplication, then restart the cloud cloudcore, and then restart the edgecore on the side.

Figure 2

Figure 3

What you expected to happen:
NodeGroups with the same name cannot be configured for EdgeApplication.

Environment:

• Kubernetes version (use kubectl version):

• KubeEdge version(e.g. cloudcore --version and edgecore --version):

• Cloud nodes Environment:

  • Hardware configuration (e.g. lscpu):
  • OS (e.g. cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Go version (e.g. go version):
  • Others:
• Edge nodes 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: