This message was deleted.
# rke2a
adamant-kite-43734
11/11/2022, 1:07 PMThis message was deleted.
c
creamy-pencil-82913
11/11/2022, 6:15 PMis your cluster out of resources ie you don’t have enough cores available to run everything?
creamy-pencil-82913
11/11/2022, 6:15 PMyou should be able to see why they are pending
s
sparse-fireman-14239
11/12/2022, 11:07 AMI assume you're hitting a bug in 1.24.6 where the CNI certificates are not renewed. It's fixed in 1.24.7
☝️ 2
h
hundreds-hairdresser-46043
11/14/2022, 7:03 AM@sparse-fireman-14239 I will do the same upgrade to 1.24.7 and see if the problem goes away - feedback to follow. Thank you for the hint
hundreds-hairdresser-46043
11/14/2022, 7:04 AM@creamy-pencil-82913 This is a clean cluster (no pods other then the core cluster and storage, they each have 4vCpu and 16gig memory) - so doubt it is a resource issue
hundreds-hairdresser-46043
11/14/2022, 8:02 AM@sparse-fireman-14239 cluster now running on v1.24.7+rke2r1. still have this problem. But now I am seeing the issue. Seems our taint setups is messing around example:
5 node(s) didn't match Pod's node affinity/selector. preemption: 0/8 nodes are available: 8 Preemption is not helpful for scheduling.
The strange thing here is - clean build works (no errors, everything deploys) , upgrades gives issue with the 3 jobs - and these 3 jobs then have issues with the taints.
29 Views