Post

Today in "weird shit Kubernetes does": did you know that if you try to do an in-place resize for a pod, the result can be one of three states?

The main way you can get into this state (aside from just "durrrr it took containerd 20 seconds longer than expected) is if you have pod requests != limits.

In this case, your pod might try to resize up, but all the other pods on the node are being greedy jerks and hogging all the resources, so kubelet's like "Welp I'll just wait for everyone else to stop being a greedy jerk 🤷"

Hey kubelet, lemme give you a clue! The other pods aren't going to stop being greedy jerks! Like, ever!