4 ms·

> we'd like the scheduler to be aware of which node has which image The kubernetes scheduler should be aware of which node has which image, that is why the Nod

> we'd like the scheduler to be aware of which node has which image The kubernetes scheduler should be aware of which node has which image, that is why the Node object has the status.images field: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#nodestatus-v1-core https://kubernetes.io/docs/reference/generated/kubernetes-ap.... It turned out to be somewhat tricky, because it increased the size of the Node object, and colocating node heartbeats onto the same object meant that a bigger object was changing relatively often. But that was addressed by moving heartbeats to a different object: https://github.com/kubernetes/enhancements/issues/589 https://github.com/kubernetes/enhancements/issues/589

paulgb 4y ago
TIL, thanks. Looks like there's a corresponding ImageLocality score used by the scheduler: https://kubernetes.io/docs/reference/scheduling/config/#scheduling-plugins https://kubernetes.io/docs/reference/scheduling/config/#sche... It doesn't get all the way to what we want, but it could be used to build a piece of it.
- cbanek 4y ago
  Very cool, I didn't know about this either. I feel like so many of these features are coming in which is great, but also part of the drag of k8s is the kind of constant upgrade churn and having to keep your yaml fresh.