-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Bugzilla 1316593: Adding information to Reclaiming Resources section #7179
Conversation
==== | ||
A PV with retention policy of `Recycle` will scrub (`rm -rf`) the data and | ||
mark it as `Available` for claim. The `Recycle` retention policy is deprecated in | ||
future versions and should be avoided. |
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.
Can you elaborate on what is meant by "future versions"? I see you have this PR labeled for 3.1 and later, so we should probably clarify. Other than that, LGTM!
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.
About from which version volume recycler is deprecated: https://github.com/openshift/openshift-docs/blob/master/release_notes/ocp_3_6_release_notes.adoc
[rev_history] |
*Recycle* are scrubbed (i.e., `rm -rf` is run on the volume) after being | ||
released from their claim (i.e, after the user's `*PersistentVolumeClaim*` bound | ||
to the volume is deleted). Once recycled, the NFS volume can be bound to a new | ||
claim. | ||
|
||
Once claim to a PV is released (that is, the is PVC deleted), the PV object |
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.
s/the is PVC deleted/the PVC is deleted/
@qinpingli Changes made, PTAL. |
LGTM |
/cherrypick enterprise-3.1 |
@tmorriso-rh: #7179 failed to apply on top of branch "enterprise-3.1":
In response to this:
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. |
/cherrypick enterprise-3.2 |
@tmorriso-rh: #7179 failed to apply on top of branch "enterprise-3.2":
In response to this:
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. |
/cherrypick enterprise-3.5-stage |
@tmorriso-rh: new pull request created: #7756 In response to this:
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. |
/cherrypick enterprise-3.6-stage |
@tmorriso-rh: new pull request created: #7757 In response to this:
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. |
/cherrypick enterprise-3.7-stage |
@tmorriso-rh: new pull request created: #7758 In response to this:
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. |
/cherrypick enterprise-3.9-stage |
@tmorriso-rh: new pull request created: #7759 In response to this:
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. |
@openshift/team-documentation PTAL.
https://bugzilla.redhat.com/show_bug.cgi?id=1316593