-
Notifications
You must be signed in to change notification settings - Fork 149
Use credentials when calling ControllerModifyVolume #544
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
base: master
Are you sure you want to change the base?
Use credentials when calling ControllerModifyVolume #544
Conversation
|
Skipping CI for Draft Pull Request. |
|
Container image for testing at |
|
/cc @sunnylovestiramisu |
Storage providers expect to obtain secrets from the ControllerMoodifyVolume CSI procedure. Without these credentials, it may not be possible to apply the parameters of a VolumeAttributeClass. A CSIPersistentVolumeSource does not have ControllerModifySecretRef (like ControllerExpandSecretRef), so in order to resolve credentials a secret reference from annotations on the PersistentVolume are used: - volume.kubernetes.io/controller-modify-secret-name - volume.kubernetes.io/controller-modify-secret-namespace In absence of these annotations, the ControllerExpandSecretRef of the CSIPersistentVolumeSource used as a fallback.
7387c5a to
c5bec27
Compare
|
@gnufied, this has been updated with the changes as discussed/proposed in the Slack #csi channel. kubernetes-csi/external-provisioner#1440 is the related change for the external-provisioner. |
Madhu-1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Madhu-1, nixpanic The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Storage providers expect to obtain secrets from the
ControllerMoodifyVolume CSI procedure. Without these credentials, it may
not be possible to apply the parameters of a VolumeAttributeClass.
A CSIPersistentVolumeSource does not have ControllerModifySecretRef
(like ControllerExpandSecretRef), so in order to resolve credentials a
secret reference from annotations on the PersistentVolume are used:
volume.kubernetes.io/controller-modify-secret-namevolume.kubernetes.io/controller-modify-secret-namespaceIn absence of these annotations, the ControllerExpandSecretRef of the
CSIPersistentVolumeSource used as a fallback.
Which issue(s) this PR fixes:
Related to kubernetes-csi/external-provisioner#1440
Special notes for your reviewer:
Posting this for early review. @gadididi is implementing
ControllerModifyVolumein Ceph-CSI and found out about the missing secrets the hard way.Approach has been discussed in a thread at #csi.
/cc carlory gnufied
Does this PR introduce a user-facing change?: