Closed ArbelNathan closed 3 years ago
This sounds completely reasonable. Mind submitting a PR?
On Mon, May 3, 2021, 4:59 AM Arbel Nathan @.***> wrote:
please consider adding volume_context to ControllerExpandVolumeRequest, it will help us with Topology support. right now we don't know the storage system of the volume in the ControllerExpandVolume call because our secret contains JSON with all the supported storage systems, only volume_context or topologies can tell us where the volume is stored.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/container-storage-interface/spec/issues/478, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAR5KLGKYL4ZXP56DHHLQ6DTLZQYXANCNFSM44AODMMA .
sure, if we are on it, could we add volume_context
to ControllerUnpublishVolumeRequest
?
No. Unpublish needs to be able to execute in the case that the CO forgets context.
On Mon, May 3, 2021, 8:43 AM Arbel Nathan @.***> wrote:
sure, if we are on it, could we add volume_context to ControllerUnpublishVolumeRequest?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/container-storage-interface/spec/issues/478#issuecomment-831234687, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAR5KLDTBPPI3X6DQSGHTLDTL2LATANCNFSM44AODMMA .
ok, tnx
please consider adding
volume_context
toControllerExpandVolumeRequest
, it will help us with Topology support. right now we don't know the storage system of the volume in theControllerExpandVolume
call because our secret contains JSON with all the supported storage systems, onlyvolume_context
ortopologies
can tell us where the volume is stored.