-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
KEP-2644: [HonorPVReclaimPolicy] Support Statically provisioned volumes #3552
Conversation
6fcef9b
to
2d45803
Compare
2d45803
to
d720ab5
Compare
@@ -197,8 +208,22 @@ Once the volume is deleted from the backend, the finalizer can be removed. This | |||
|
|||
Note: This feature should work with CSI Migration disabled or enabled. | |||
|
|||
#### Statically Provisioned volumes | |||
|
|||
The finalizer `external-provisioner.volume.kubernetes.io/finalizer` is added only to statically provisioned volumes that are associated with a PVC. |
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.
Will PV controller add the finalizer? Why is finalizer kubernetes.io/pv-controller
not used here?
IMO, the finalizers should be the same as with dynamically provisioned volumes. I would not event mention it as a separate chapter, I would mention that statically provisioned volumes will behave the same as dynamically provisioned ones, except for "PV is not (yet?) associated with a PVC".
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.
Since it is a CSI driver volume external-provisioner.volume.kubernetes.io/finalizer
is added, this is added by the external-provisioner. kubernetes.io/pv-controller
is added to in-tree volumes.
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.
I've addressed the comment, removed the statically and dynamically provisioned volumes section, and merged them into one as you specified.
d720ab5
to
4369d82
Compare
Signed-off-by: Deepak Kinni <dkinni@vmware.com>
4369d82
to
d55c5cf
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deepakkinni, jsafrane The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
KEP-2644: [HonorPVReclaimPolicy] Support Statically provisioned volumes
One-line PR description: Support Statically provisioned volumes
Issue link: Always Honor PersistentVolume Reclaim Policy #2644
Other comments:
Signed-off-by: Deepak Kinni dkinni@vmware.com