mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-08-16 23:29:21 +00:00
resourceclaim controller: avoid caching deleted pod unnecessarily
We don't need to remember that a pod got deleted when it had no resource claims because the code which checks the cached UIDs only checks for pods which have resource claims.
This commit is contained in:
parent
a8b90c9008
commit
98ba89d31d
@ -202,15 +202,15 @@ func (ec *Controller) enqueuePod(logger klog.Logger, obj interface{}, deleted bo
|
|||||||
return
|
return
|
||||||
}
|
}
|
||||||
|
|
||||||
if deleted {
|
|
||||||
ec.deletedObjects.Add(pod.UID)
|
|
||||||
}
|
|
||||||
|
|
||||||
if len(pod.Spec.ResourceClaims) == 0 {
|
if len(pod.Spec.ResourceClaims) == 0 {
|
||||||
// Nothing to do for it at all.
|
// Nothing to do for it at all.
|
||||||
return
|
return
|
||||||
}
|
}
|
||||||
|
|
||||||
|
if deleted {
|
||||||
|
ec.deletedObjects.Add(pod.UID)
|
||||||
|
}
|
||||||
|
|
||||||
logger.V(6).Info("pod with resource claims changed", "pod", klog.KObj(pod), "deleted", deleted)
|
logger.V(6).Info("pod with resource claims changed", "pod", klog.KObj(pod), "deleted", deleted)
|
||||||
|
|
||||||
// Release reservations of a deleted or completed pod?
|
// Release reservations of a deleted or completed pod?
|
||||||
|
Loading…
Reference in New Issue
Block a user