Wireguard backend has duplicate peers

[txomon]

Expected Behavior

Running wg should show one link per node

Current Behavior

Running wg may show more than one link per node

Possible Solution

Probably check for existing peers before adding a new one

Steps to Reproduce (for bugs)

Set up several nodes with wireguard backend, check all of them

Context

Thankfully it doesn't break functionality so it's not such a big problem, but maybe something could be done

Your Environment

• Flannel version: master
• Backend used (e.g. vxlan or udp): wireguard
• Etcd version: N/A
• Kubernetes version (if used): 1.20
• Operating System and version: arch + k3s
• Link to your project (optional): None

[nabam]

I think I experience exactly the same issue here https://github.com/k3s-io/k3s/issues/5216. Flannel is a bit outdated in the k3s version that I'm running, not sure if it's fixed in later releases of flannel.

[andreek]

This issue is solved by #1230.

Can be closed.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.