Why is VolumeAttributes not passed in csi.DeleteVolumeRequest?

[avagin]

VolumeAttributes can contains properties which may be useful for deleting volumes.

[sarjeet2013]

+1.

DeleteVolume may require additional info to fulfill the delete request which can be provided by VolumeAttributes passed to DeleteVolume along with volumeId and Secrets.

[xing-yang]

@sarjeet2013 Can you use Secrets to store the server info you need?
See https://github.com/container-storage-interface/spec/blob/master/spec.md#secrets-requirements and
https://kubernetes.io/docs/concepts/configuration/secret/

[sarjeet2013]

@xing-yang I discussed it internally but it seems an overhead in adding server info as secret (which doesn't make sense at all) which can be passed easily as parameters from StorageClass.

Also, it adds another resource (server info Secret) to be created before StorageClass is created.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[msau42]

This is a question for the CSI spec.

Related discussions:
container-storage-interface/spec#29
container-storage-interface/spec#216
container-storage-interface/spec#167

[msau42]

/close

[k8s-ci-robot]

@msau42: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.