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
Copy file name to clipboardExpand all lines: keps/sig-storage/1790-recover-resize-failure/README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -262,6 +262,9 @@ The complete expansion and recovery flow of both control-plane and kubelet is do
262
262
so it should not break any of existing automation. This means that if `pvc.Status.AllocatedResources` is available it will be
263
263
used for calculating quota.
264
264
265
+
To facilitate older kubelets - external resize controller will set `pvc.Status.ResizeStatus` to "''" after entire expansion process is complete. This will ensure that `ResizeStatus` is updated
266
+
after expansion is complete even with older kubelets. No recovery from expansion failure will be possible in this case and the workaround will be removed once feature goes GA.
267
+
265
268
One more thing to keep in mind is - enabling this feature in kubelet while keeping it disabled in external-resizer will cause
266
269
all volume expansions operations to get stuck(similar thing will happen when feature moves to beta and kubelet is newer but external-resizer sidecar is older).
267
270
This limitation will be documented in external-resizer.
0 commit comments