@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.