File tree Expand file tree Collapse file tree 1 file changed +7
-2
lines changed
keps/sig-storage/1472-storage-capacity-tracking Expand file tree Collapse file tree 1 file changed +7
-2
lines changed Original file line number Diff line number Diff line change @@ -1259,8 +1259,13 @@ CSIStorageCapacity API for node-local storage as follows:
1259
1259
A proof-of-concept of this approach is available in
1260
1260
https://github.com/kubernetes/autoscaler/pull/3887 and has been used
1261
1261
successfully to scale an Azure cluster up and down with csi-driver-host-path as
1262
- CSI driver. Because of the lack of storage capacity modeling, scale up happens
1263
- slowly. To address that, the scheduler would have to take volumes that are in
1262
+ CSI driver. However, due to the lack of storage capacity modeling, scale up
1263
+ happens slowly and configuring the cluster correctly is complex. Whether that
1264
+ is good enough or insufficient depends on the use cases for storage in a
1265
+ cluster where autoscaling is enabled. The current understanding is that further
1266
+ work is needed.
1267
+
1268
+ To improve scale up speed, the scheduler would have to take volumes that are in
1264
1269
the process of being provisioned into account when deciding about other
1265
1270
suitable nodes. This might not be the right decision for all CSI drivers, so
1266
1271
further exploration and potentially an extension of the CSI API ("total
You can’t perform that action at this time.
0 commit comments