Skip to content

Commit 3175f6b

Browse files
committed
GetCapacityResponse: promote maximum_volume_size
Kubernetes and several CSI drivers have been using that field for a while now and no changes to the semantic are expected, therefore the alpha status can and should be removed. The minimum_volume_size field is not used by Kubernetes. The semantic is probably stable, but further practical experience with it might be desirable before promoting it.
1 parent 5b0d454 commit 3175f6b

File tree

3 files changed

+245
-245
lines changed

3 files changed

+245
-245
lines changed

csi.proto

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -988,8 +988,7 @@ message GetCapacityResponse {
988988
// a maximum size for individual volumes and leave it unset
989989
// otherwise. COs MAY use it to make decision about
990990
// where to create volumes.
991-
google.protobuf.Int64Value maximum_volume_size = 2
992-
[(alpha_field) = true];
991+
google.protobuf.Int64Value maximum_volume_size = 2;
993992

994993
// The smallest size that may be used in a
995994
// CreateVolumeRequest.capacity_range.limit_bytes field

0 commit comments

Comments
 (0)