Patrick Ohly 1b47e6433b dra delayed allocation: deallocate when a pod is done ...

This releases the underlying resource sooner and ensures that another consumer
can get scheduled without being influenced by a decision that was made for the
previous consumer.

An alternative would have been to have the apiserver trigger the deallocation
whenever it sees the `status.reservedFor` getting reduced to zero. But that
then also triggers deallocation when kube-scheduler removes the last
reservation after a failed scheduling cycle. In that case we want to keep the
claim allocated and let the kube-scheduler decide on a case-by-case basis which
claim should get deallocated.

2023-06-29 09:47:30 +02:00

..

metrics

…

controller_test.go

api: resource.k8s.io v1alpha1 -> v1alpha2

2023-03-14 07:52:03 +01:00

controller.go

dra delayed allocation: deallocate when a pod is done

2023-06-29 09:47:30 +02:00

doc.go

…

OWNERS

…

uid_cache.go

…