Open houshengbo opened 2 months ago
If the over-ratio is set to 100, the bug was fixed with the PR opened.
However, if there is only one pod running for the old revision, there is nothing we can do from the logic, because it may take longer time for Kubernetes to add the field DeletionTimestamp
into the pod.
If there is only one pod, or overratio set to 100, using resourceUtil strategy won't directly kill the old pods immediately.