You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix a bug where the target pod doesn't become schedulable within 5 minutes when a deleted pod uses the same PVC with the ReadWriteOncePod access mode. (kubernetes#126263)
@@ -375,9 +374,30 @@ func (pl *VolumeRestrictions) isSchedulableAfterPodDeleted(logger klog.Logger, p
375
374
376
375
nodeInfo:=framework.NewNodeInfo(deletedPod)
377
376
if!satisfyVolumeConflicts(pod, nodeInfo) {
377
+
logger.V(5).Info("Pod with the volume that the target pod requires was deleted, which might make this pod schedulable", "pod", klog.KObj(pod), "deletedPod", klog.KObj(deletedPod))
378
378
returnframework.Queue, nil
379
379
}
380
380
381
+
// Return Queue if a deleted pod uses the same PVC since the pod may be unschedulable due to the ReadWriteOncePod access mode of the PVC.
382
+
//
383
+
// For now, we don't actually fetch PVC and check the access mode because that operation could be expensive.
384
+
// Once the observability around QHint is established,
385
+
// we may want to do that depending on how much the operation would impact the QHint latency negatively.
logger.V(5).Info("Pod with the same PVC that the target pod requires was deleted, which might make this pod schedulable", "pod", klog.KObj(pod), "deletedPod", klog.KObj(deletedPod))
396
+
returnframework.Queue, nil
397
+
}
398
+
}
399
+
400
+
logger.V(5).Info("An irrelevant Pod was deleted, which doesn't make this pod schedulable", "pod", klog.KObj(pod), "deletedPod", klog.KObj(deletedPod))
0 commit comments