Missing capacity field in NodePublishVolumeRequest

[ne0h]

Is your feature request related to a problem?/Why is this needed
NodePublishVolumeRequest does not have a field indicating the desired capacity of a request.
But the capacity would be quite helpful to expose local storage of the node.

Describe the solution you'd like in detail
Adding a new field CapacityRange capacity_range = 9; to NodePublishVolumeRequest.

Describe alternatives you've considered
It would be possible to look into another resource to read the capacity (Kubernetes persistent volume claims in my case). But that call would require additional permissions and additional calls.

Additional context
n/a

I could provide the required change :)

[jdef]

The use case isn't clear to me. But you mention k8s, so is there a related KEP? Or something else that describes the scenario you're solving for from the perspective of the CO? James DeFelice

…

On Mon, Apr 7, 2025, 9:25 AM Maximilian Heß ***@***.***> wrote: *Is your feature request related to a problem?/Why is this needed* NodePublishVolumeRequest does not have a field indicating the desired capacity of a request. But the capacity would be quite helpful to expose local storage of the node. *Describe the solution you'd like in detail* Adding a new field CapacityRange capacity_range = 9; to NodePublishVolumeRequest. *Describe alternatives you've considered* It would be possible to look into another resource to read the capacity (Kubernetes persistent volume claims in my case). But that call would require additional permissions and additional calls. *Additional context* n/a — Reply to this email directly, view it on GitHub <#583>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR5KLBLLXC22UF7VK6OAU32YJ4D7AVCNFSM6AAAAAB2TTRNR6VHI2DSMVQWIX3LMV43ASLTON2WKOZSHE3TMOBWGMYTOMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> [image: ne0h]*ne0h* created an issue (container-storage-interface/spec#583) <#583> *Is your feature request related to a problem?/Why is this needed* NodePublishVolumeRequest does not have a field indicating the desired capacity of a request. But the capacity would be quite helpful to expose local storage of the node. *Describe the solution you'd like in detail* Adding a new field CapacityRange capacity_range = 9; to NodePublishVolumeRequest. *Describe alternatives you've considered* It would be possible to look into another resource to read the capacity (Kubernetes persistent volume claims in my case). But that call would require additional permissions and additional calls. *Additional context* n/a — Reply to this email directly, view it on GitHub <#583>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR5KLBLLXC22UF7VK6OAU32YJ4D7AVCNFSM6AAAAAB2TTRNR6VHI2DSMVQWIX3LMV43ASLTON2WKOZSHE3TMOBWGMYTOMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>