CI service backed up for > 3 hours this morning. Logged in to find out the backing K8s has deadlocked the scheduler between our requests / limits, and node pool sizes.

🤔 so, the scheduler wont back off if the autoscaler shits out and says "no more capacity configured"?

That feels like an oversight... on my part...

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!