This message was deleted.
# rke2
a
This message was deleted.
a
Actually now this is happening in my other prod cluster and one of my test clusters. All from a k3s upgrade.
For anyone watching, the issue ended up being a lingering manager node that I had deleted from the local cluster, but it was still running in ec2. Once I found the node in ec2 and terminated it, my downstream cluster was happy again. And just to be clear, that node was nowhere to be found in the local cluster, no pods were running on it, etc...
p
I hate the "context deadline exceeded" errors. They basically mean "something deep down the stack is fucked" and good luck finding out what...