Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to pass UserCredentials in Create/Delete Image #28

Closed
rootfs opened this issue Jan 18, 2018 · 1 comment
Closed

Need to pass UserCredentials in Create/Delete Image #28

rootfs opened this issue Jan 18, 2018 · 1 comment

Comments

@rootfs
Copy link
Contributor

rootfs commented Jan 18, 2018

Currently storage class doesn't have credentials API, external-provisioner passes everything into Parameters but not into UserCredentials.

This is a problem for certain volumes such as rbd. We currently use parameters to store plaint text secret to get around this issue.

Ideally credentials should still be encoded as a K8S Secret. External provisioner needs a mechanism to get credentials from StorageClass, either through a special parameter, annotation, or new API fields, then passes these credentials into UserCredentials in CreateVolume and DeleteVolume calls.

thanks @sbezverk for his early investigation into this issue

@rootfs
Copy link
Contributor Author

rootfs commented Jan 19, 2018

per http://blog.kubernetes.io/2018/01/introducing-container-storage-interface.html, credentials are not supported in alpha. Closing.

@rootfs rootfs closed this as completed Jan 19, 2018
jsafrane pushed a commit to jsafrane/external-provisioner that referenced this issue Sep 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant