This message was deleted.
# rke2a
adamant-kite-43734
08/24/2022, 5:04 AMThis message was deleted.
c
creamy-pencil-82913
08/24/2022, 5:59 AMHave you looked at the kube-vip logs? This is all kube-vip stuff, not rke2 specific really.
n
narrow-noon-75604
08/24/2022, 6:00 AMI guess this might be because of etcd latency as mentioned in a similar issue - https://github.com/Azure/aks-hci/issues/167
narrow-noon-75604
08/24/2022, 6:10 AMPlease find the logs of 3 VIP pods -
Copy code
$ kubectl logs kube-vip-ds-554th -n kube-system
time="2022-08-24T06:03:39Z" level=info msg="Starting <http://kube-vip.io|kube-vip.io> [v0.5.0]"
time="2022-08-24T06:03:39Z" level=info msg="namespace [kube-system], Mode: [ARP], Features(s): Control Plane:[true], Services:[true]"
time="2022-08-24T06:03:39Z" level=info msg="prometheus HTTP server started"
time="2022-08-24T06:03:39Z" level=info msg="Starting Kube-vip Manager with the ARP engine"
time="2022-08-24T06:03:39Z" level=info msg="beginning services leadership, namespace [kube-system], lock name [plndr-svcs-lock], id [<http://master3.192.168.10.73.nip.io|master3.192.168.10.73.nip.io>]"
I0824 06:03:39.600009 1 leaderelection.go:248] attempting to acquire leader lease kube-system/plndr-svcs-lock...
time="2022-08-24T06:03:39Z" level=info msg="Beginning cluster membership, namespace [kube-system], lock name [plndr-cp-lock], id [<http://master3.192.168.10.73.nip.io|master3.192.168.10.73.nip.io>]"
I0824 06:03:39.600649 1 leaderelection.go:248] attempting to acquire leader lease kube-system/plndr-cp-lock...
time="2022-08-24T06:03:39Z" level=info msg="Node [<http://master2.192.168.10.72.nip.io|master2.192.168.10.72.nip.io>] is assuming leadership of the cluster"
time="2022-08-24T06:03:39Z" level=info msg="new leader elected: <http://master2.192.168.10.72.nip.io|master2.192.168.10.72.nip.io>"
--------------------------------------------------------------------------------------------------------
$ kubectl logs kube-vip-ds-rqhn5 -n kube-system
time="2022-08-24T06:05:17Z" level=info msg="Starting <http://kube-vip.io|kube-vip.io> [v0.5.0]"
time="2022-08-24T06:05:17Z" level=info msg="namespace [kube-system], Mode: [ARP], Features(s): Control Plane:[true], Services:[true]"
time="2022-08-24T06:05:17Z" level=info msg="prometheus HTTP server started"
time="2022-08-24T06:05:17Z" level=info msg="Starting Kube-vip Manager with the ARP engine"
time="2022-08-24T06:05:17Z" level=info msg="beginning services leadership, namespace [kube-system], lock name [plndr-svcs-lock], id [<http://master2.192.168.10.72.nip.io|master2.192.168.10.72.nip.io>]"
I0824 06:05:17.604621 1 leaderelection.go:248] attempting to acquire leader lease kube-system/plndr-svcs-lock...
time="2022-08-24T06:05:17Z" level=info msg="Beginning cluster membership, namespace [kube-system], lock name [plndr-cp-lock], id [<http://master2.192.168.10.72.nip.io|master2.192.168.10.72.nip.io>]"
I0824 06:05:17.605137 1 leaderelection.go:248] attempting to acquire leader lease kube-system/plndr-cp-lock...
time="2022-08-24T06:05:17Z" level=info msg="new leader elected: <http://master1.192.168.10.71.nip.io|master1.192.168.10.71.nip.io>"
time="2022-08-24T06:05:17Z" level=info msg="Node [<http://master3.192.168.10.73.nip.io|master3.192.168.10.73.nip.io>] is assuming leadership of the cluster"
--------------------------------------------------------------------------------------------------------
$ kubectl logs kube-vip-ds-vdwdq -n kube-system
time="2022-08-24T06:03:33Z" level=info msg="Starting <http://kube-vip.io|kube-vip.io> [v0.5.0]"
time="2022-08-24T06:03:33Z" level=info msg="namespace [kube-system], Mode: [ARP], Features(s): Control Plane:[true], Services:[true]"
time="2022-08-24T06:03:33Z" level=info msg="prometheus HTTP server started"
time="2022-08-24T06:03:33Z" level=info msg="Starting Kube-vip Manager with the ARP engine"
time="2022-08-24T06:03:33Z" level=info msg="beginning services leadership, namespace [kube-system], lock name [plndr-svcs-lock], id [<http://master1.192.168.10.71.nip.io|master1.192.168.10.71.nip.io>]"
I0824 06:03:33.407599 1 leaderelection.go:248] attempting to acquire leader lease kube-system/plndr-svcs-lock...
time="2022-08-24T06:03:33Z" level=info msg="Beginning cluster membership, namespace [kube-system], lock name [plndr-cp-lock], id [<http://master1.192.168.10.71.nip.io|master1.192.168.10.71.nip.io>]"
I0824 06:03:33.408068 1 leaderelection.go:248] attempting to acquire leader lease kube-system/plndr-cp-lock...
time="2022-08-24T06:03:33Z" level=info msg="new leader elected: <http://master2.192.168.10.72.nip.io|master2.192.168.10.72.nip.io>"
time="2022-08-24T06:03:33Z" level=info msg="Node [<http://master2.192.168.10.72.nip.io|master2.192.168.10.72.nip.io>] is assuming leadership of the cluster"
time="2022-08-24T06:05:07Z" level=info msg="Node [<http://master3.192.168.10.73.nip.io|master3.192.168.10.73.nip.io>] is assuming leadership of the cluster"
I0824 06:05:11.368625 1 leaderelection.go:258] successfully acquired lease kube-system/plndr-svcs-lock6 Views