Skip to content

Commit 73cb6a3

Browse files
committed
storage capacity tracking: emphasize limitations more strongly
1 parent 8115cbc commit 73cb6a3

File tree

1 file changed

+7
-2
lines changed
  • keps/sig-storage/1472-storage-capacity-tracking

1 file changed

+7
-2
lines changed

keps/sig-storage/1472-storage-capacity-tracking/README.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1259,8 +1259,13 @@ CSIStorageCapacity API for node-local storage as follows:
12591259
A proof-of-concept of this approach is available in
12601260
https://github.com/kubernetes/autoscaler/pull/3887 and has been used
12611261
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
12641269
the process of being provisioned into account when deciding about other
12651270
suitable nodes. This might not be the right decision for all CSI drivers, so
12661271
further exploration and potentially an extension of the CSI API ("total

0 commit comments

Comments
 (0)