This message was deleted.
# k3sa
adamant-kite-43734
07/19/2022, 2:51 PMThis message was deleted.
c
crooked-rocket-3338
07/19/2022, 2:55 PMDo you guys know a cleaner way to handle this rather that
rm -rf /var/lib/cni/networks/cbr0/*c
creamy-pencil-82913
07/19/2022, 4:44 PMThat issue is with RKE. Are you using RKE, or K3s?
creamy-pencil-82913
07/19/2022, 4:44 PMK3s doesn’t use kube-router for anything but network policy, it is not involved in the CNI stack at all.
c
crooked-rocket-3338
07/19/2022, 6:46 PMI am using k3s so this is definitely not the same issue. Do you know what can lead to
failed to allocate for range 0: no IP addresses available in range set: 10.42.1.1-10.42.1.254c
creamy-pencil-82913
07/19/2022, 7:21 PMHow many pods do you have running on the node?
creamy-pencil-82913
07/19/2022, 7:22 PMdid you raise MaxPods without changing the cidr size?
c
crooked-rocket-3338
07/19/2022, 7:22 PMnope I got 20/25 pods but still not IP available after a while.
c
creamy-pencil-82913
07/19/2022, 7:22 PMI’m confused as to why it would even be allocating pod ranges for a load balancer. ServiceLB doesn’t allocate IPs, it just uses the node IPs. Did you deploy your own LB controller?
creamy-pencil-82913
07/19/2022, 7:23 PMIt might be helpful if you opened a GH issue in the k3s repo and attached the complete service logs from the node in question
creamy-pencil-82913
07/19/2022, 7:24 PMsometimes if you just google a snippet of an error message you can end up troubleshooting a completely unrelated issue
👀 1
c
crooked-rocket-3338
07/19/2022, 7:24 PMpretty much everything is stock default k3s unless I did something completely wrong without noticing. But I try not to bring anything that "is my own" 🙂
crooked-rocket-3338
07/19/2022, 7:26 PMOk will try to gather more info and open a GH issue.
crooked-rocket-3338
07/20/2022, 2:04 PMcreated and issue here : https://github.com/k3s-io/k3s/issues/5885
157 Views