How should network interfaces look like when kube-...
# rke2
r
How should network interfaces look like when kube-vip gets ip from Harvester Cloud Provider on rocky-linux? I just can't connect via the vip. kube-vip creates a new interfaace and ist not attached to the eth0 interface. Is this normal?
Copy code
time="2025-05-05T13:40:56Z" level=info msg="Starting kube-vip.io [v0.8.7]"
time="2025-05-05T13:40:56Z" level=info msg="namespace [kube-system], Mode: [ARP], Features(s): Control Plane:[false], Services:[true]"
time="2025-05-05T13:40:56Z" level=info msg="prometheus HTTP server started"
time="2025-05-05T13:40:56Z" level=warning msg="Node name is missing from the config, fall back to hostname"
time="2025-05-05T13:40:56Z" level=info msg="Using node name [fa4-pool1-jnfjx-hlq6v]"
time="2025-05-05T13:40:56Z" level=info msg="Starting Kube-vip Manager with the ARP engine"
time="2025-05-05T13:40:56Z" level=info msg="beginning services leadership, namespace [kube-system], lock name [plndr-svcs-lock], id [fa4-pool1-jnfjx-hlq6v]"
time="2025-05-05T13:40:56Z" level=info msg="Starting UPNP Port Refresher"
I0505 13:40:56.511522       1 leaderelection.go:250] attempting to acquire leader lease kube-system/plndr-svcs-lock...
I0505 13:40:57.130721       1 leaderelection.go:260] successfully acquired lease kube-system/plndr-svcs-lock
time="2025-05-05T13:40:57Z" level=info msg="(svcs) starting services watcher for all namespaces"
time="2025-05-05T13:40:57Z" level=info msg="Creating new macvlan interface for DHCP [vip-9658373b]"
time="2025-05-05T13:40:57Z" level=info msg="New interface [vip-9658373b] mac is 00:00:6c:f4:96:0a"
time="2025-05-05T13:40:57Z" level=info msg="(svcs) adding VIP [10.31.241.232] via vip-9658373b for [kube-system/rke2-ingress-nginx-controller]"
time="2025-05-05T13:40:57Z" level=info msg="[service] synchronised in 633ms""
ip addr looks like this:
Copy code
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 66:36:a9:bf:d1:b6 brd ff:ff:ff:ff:ff:ff
    altname enp1s0
    inet 10.31.241.231/28 brd 10.31.241.239 scope global dynamic noprefixroute eth0
       valid_lft 86270sec preferred_lft 86270sec
    inet6 fe80::6436:a9ff:febf:d1b6/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: cali4cb71518fd0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000
    link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff link-netns cni-959ae84e-bc74-9786-5b09-8c201f8cde35
    inet6 fe80::ecee:eeff:feee:eeee/64 scope link
       valid_lft forever preferred_lft forever
...
16: vip-9658373b@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 00:00:6c:f4:96:0a brd ff:ff:ff:ff:ff:ff
    inet 10.31.241.232/28 brd 10.31.241.239 scope global vip-9658373b
       valid_lft forever preferred_lft forever
    inet6 fe80::200:6cff:fef4:960a/64 scope link
       valid_lft forever preferred_lft forever
17: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default
    link/ether 22:69:20:7c:b6:ac brd ff:ff:ff:ff:ff:ff
    inet 10.42.0.0/32 scope global flannel.1
       valid_lft forever preferred_lft forever
    inet6 fe80::2069:20ff:fe7c:b6ac/64 scope link
       valid_lft forever preferred_lft forever
20: cali1ee45b0a9e6@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000
    link/ether ee:ee:ee:ee:ee:ee brd ff:ff:ff:ff:ff:ff link-netns cni-62900864-5ccc-091e-6c35-6a94a682c942
    inet6 fe80::ecee:eeff:feee:eeee/64 scope link
       valid_lft forever preferred_lft forever