[Release-1.29] - 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.29.5+k3s-fa351253 (fa351253)

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:

 
 
 

 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   105m   v1.29.5+k3s-fa351253
node/ip-1 .us-west-1.compute.internal   Ready    control-plane,etcd,master   107m   v1.29.5+k3s-fa351253
node/ip- .us-west-1.compute.internal   Ready    control-plane,etcd,master   104m   v1.29.5+k3s-fa351253
node/ip- .us-west-1.compute.internal     Ready    <none>                      103m   v1.29.5+k3s-fa351253

NAMESPACE     NAME                                                 READY   STATUS      RESTARTS      AGE
default       pod/dualstack-ing-ds-658b2                           1/1     Running     0             102m
default       pod/dualstack-ing-ds-8wjw6                           1/1     Running     1 (79s ago)   102m
default       pod/dualstack-ing-ds-d5zj9                           1/1     Running     0             102m
default       pod/dualstack-ing-ds-tk7qk                           1/1     Running     0             102m
default       pod/dualstack-nodeport-deployment-749c4fb477-5mw7b   1/1     Running     0             102m
default       pod/dualstack-nodeport-deployment-749c4fb477-8rm7l   1/1     Running     0             102m
default       pod/dualstack-nodeport-deployment-749c4fb477-gslv6   1/1     Running     1 (79s ago)   102m
default       pod/dualstack-nodeport-deployment-749c4fb477-m6ctx   1/1     Running     0             102m
default       pod/httpd-deployment-84b5f79979-b4kdx                1/1     Running     0             100m
default       pod/httpd-deployment-84b5f79979-nqzpc                1/1     Running     0             100m
kube-system   pod/coredns-6799fbcd5-6gr7j                          1/1     Running     1 (79s ago)   106m
kube-system   pod/helm-install-traefik-crd-86nmg                   0/1     Completed   0             106m
kube-system   pod/helm-install-traefik-z2nxp                       0/1     Completed   1             106m
kube-system   pod/local-path-provisioner-6c86858495-qwnxc          1/1     Running     1 (79s ago)   106m
kube-system   pod/metrics-server-54fd9b65b-pdvrc                   1/1     Running     1 (79s ago)   106m
kube-system   pod/svclb-traefik-18cc449a-bxxlc                     2/2     Running     0             105m
kube-system   pod/svclb-traefik-18cc449a-gnmvq                     2/2     Running     0             103m
kube-system   pod/svclb-traefik-18cc449a-j688r                     2/2     Running     0             104m
kube-system   pod/svclb-traefik-18cc449a-pz9nq                     2/2     Running     2 (79s ago)   106m
kube-system   pod/traefik-7d5f6474df-xrgph                         1/1     Running     1 (79s ago)   106m