KEP-1287: Clarify resize retry behavior

Author: tallclair

keps/sig-node/1287-in-place-update-pod-resources/README.md

@@ -307,7 +307,7 @@ This field can be set to one of the following values:
   `Infeasible` resize will take precedence over `InProgress`.
   Desired resources == Allocated resources != Actual resources.
 * `Deferred` - the proposed resize is feasible in theory (it fits on this node)
-  but is not possible right now; it will be re-evaluated.
+  but is not possible right now; it will be re-evaluated on every pod sync.
   Desired resources != Allocated resources.
 * `Infeasible` - the proposed resize is not feasible and is rejected; it will not
   be re-evaluated. Desired resources != Allocated resources.
@@ -771,6 +771,9 @@ When a resize CRI request succeeds, the pod will be marked for resync to read th
 the actual configured resources do not match the desired resources, this will be reflected in the
 pod status resources, but not otherwise acted upon.
 
+If a resize request does not succeed, the Kubelet will retry the resize on every subsequent pod
+sync, until it succeeds or the container is terminated.
+
 ### Memory Limit Decreases
 
 Setting the memory limit below current memory usage can cause problems. If the kernel cannot reclaim