Weird. A reboot would not resolve but I stopped rke2 server process, deleted the pod with --force, then rke2-killall.sh and then restarted rke2 server process and it corrected itself.
witty-xylophone-10946
04/05/2024, 11:01 PM
I tried adding second node and I am seeing similar with other kube-system pods. I'll try the same thing for these. The duplicate IPs patch of Pods is interesting. Currently they are kube-scheduler and kube-proxy "failing to to update status for pod" with Duplicate IP for same IPFamily.
I am running RHEL 8.8 4.18.