Add volume_context to ControllerExpandVolumeRequest

Question

Add volume_context to ControllerExpandVolumeRequest

ArbelNathan opened this issue 4 years ago · 4 comments

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.

ArbelNathan commented 4 years ago

ok, tnx

Answer 1 · 2021-05-03T11:34:30.000Z

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 <#478>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR5KLGKYL4ZXP56DHHLQ6DTLZQYXANCNFSM44AODMMA> .

Answer 2 · 2021-05-03T12:43:34.000Z

sure, if we are on it, could we add volume_context to ControllerUnpublishVolumeRequest?

Answer 3 · 2021-05-03T13:49:27.000Z

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 <#478 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAR5KLDTBPPI3X6DQSGHTLDTL2LATANCNFSM44AODMMA> .