[Release-1.28] - flannel-v6.1 MAC address changes every boot

[thomasferrandiz]

Backport fix for flannel-v6.1 MAC address changes every boot

• flannel-v6.1 MAC address changes every boot #9957

[fmoral2]

Validated on Version:

-$ k3s version v1.28.10+k3s-7b8f0e1b (7b8f0e1b)

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
Ubuntu
AMD
DUAL STACK

Cluster Configuration:
-3 nodes

Steps to validate the fix

1. start k3s with flannel-backend: vxlan
2. reboot node A
3. Validate that flannel ipv6 mac addrs is not changed
4. Validate other nodes can communicate
5. Validate nodes and pods

Reproduction Issue:

 
 k3s version v1.28.10+k3s-7b8f0e1b (7b8f0e1b)
 

 ip link show flannel-v6.1
 flannel-v6.1 MAC address: [redacted]-1

 reboot
ip link show flannel-v6.1
 flannel-v6.1 MAC address: [redacted]-23


NODE B AND C:
 $ ping6 0000:cafe:00::

no connection

Validation Results:

  ip link show flannel-v6.1
 flannel-v6.1 MAC address: [redacted]-1f

 reboot
ip link show flannel-v6.1
 flannel-v6.1 MAC address: [redacted]-1f


 NODE B and C:

 $ ping6 0000:cafe:00::
 
 
--- 0000:cafe:00:: ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2009ms
rtt min/avg/max/mdev = 0.248/0.526/0.992/0.331 ms

 $ kubectl get nodes,pods -A
 
 NAME                                                STATUS   ROLES                       AGE    VERSION
node/ip- .us-west-1.compute.internal   Ready    control-plane,etcd,master   106m   v1.28.10+k3s-7b8f0e1b
node/ip- 8.us-west-1.compute.internal   Ready    control-plane,etcd,master   106m   v1.28.10+k3s-7b8f0e1b
node/ip- .us-west-1.compute.internal   Ready    <none>                      105m   v1.28.10+k3s-7b8f0e1b
node/ip- 3.us-west-1.compute.internal    Ready    control-plane,etcd,master   108m   v1.28.10+k3s-7b8f0e1b

NAMESPACE     NAME                                                 READY   STATUS      RESTARTS      AGE
default       pod/dualstack-ing-ds-7gb5f                           1/1     Running     0             105m
default       pod/dualstack-ing-ds-mzh6r                           1/1     Running     1 (72s ago)   105m
default       pod/dualstack-ing-ds-rx4jx                           1/1     Running     0             105m
default       pod/dualstack-ing-ds-zpss7                           1/1     Running     0             105m
default       pod/dualstack-nodeport-deployment-749c4fb477-2jdcj   1/1     Running     1 (72s ago)   104m
default       pod/dualstack-nodeport-deployment-749c4fb477-2kv2q   1/1     Running     0             104m
default       pod/dualstack-nodeport-deployment-749c4fb477-jd7mw   1/1     Running     0             104m
default       pod/dualstack-nodeport-deployment-749c4fb477-mnbmh   1/1     Running     0             104m
default       pod/httpd-deployment-84b5f79979-lrf4s                1/1     Running     0             103m
default       pod/httpd-deployment-84b5f79979-vnw4r                1/1     Running     0             103m
kube-system   pod/coredns-6799fbcd5-5gntl                          1/1     Running     1 (72s ago)   108m
kube-system   pod/helm-install-traefik-bbkrf                       0/1     Completed   1             108m
kube-system   pod/helm-install-traefik-crd-npj4h                   0/1     Completed   0             108m
kube-system   pod/local-path-provisioner-6c86858495-66vf8          1/1     Running     1 (72s ago)   108m
kube-system   pod/metrics-server-54fd9b65b-xhnff                   1/1     Running     1 (72s ago)   108m
kube-system   pod/svclb-traefik-dd187904-4zgzd                     2/2     Running     0             106m
kube-system   pod/svclb-traefik-dd187904-gdpvs                     2/2     Running     0             105m
kube-system   pod/svclb-traefik-dd187904-hbnwq                     2/2     Running     0             106m
kube-system   pod/svclb-traefik-dd187904-vgfrq                     2/2     Running     2 (72s ago)   108m
kube-system   pod/traefik-7d5f6474df-dczxb                         1/1     Running     1 (72s ago)   108m