Bug 1304529 - iSCSI example PV/PVC is missing a persistentVolumeReclaimPolicy
Summary: iSCSI example PV/PVC is missing a persistentVolumeReclaimPolicy
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: ---
Assignee: Thien-Thi Nguyen
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-03 22:44 UTC by Eric Jones
Modified: 2019-09-12 09:53 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-18 15:29:45 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Eric Jones 2016-02-03 22:44:20 UTC
Document URL: 
https://access.redhat.com/documentation/en/openshift-enterprise/version-3.1/installation-and-configuration/#using-iscsi

Section Number and Name: 
13.8. PERSISTENT STORAGE USING ISCSI

Describe the issue: 
PV/PVC setup with iSCSI does not include `persistentVolumeReclaimPolicy: "Recycle"` or any other reference to the Reclaim Policy. Which means when a PVC is deleted after binding to that PV it does not know what to do.

Suggestions for improvement: 
Include `persistentVolumeReclaimPolicy: "Recycle"` in the example.

Comment 1 Thien-Thi Nguyen 2016-03-17 21:13:53 UTC
Hi Huamin,

I believe iSCSI does not support the ‘Recycle’ policy, according to:
- https://docs.openshift.com/enterprise/3.1/architecture/additional_concepts/storage.html#pv-recycling-policy
(which states that only NFS and HostPath support recycling).

Is this correct?

Comment 3 hchen 2016-03-18 13:21:48 UTC
yes, that's my understanding too. Currently only NFS supports recycling in production.

Comment 4 Thien-Thi Nguyen 2016-03-18 15:29:45 UTC
(In reply to hchen from comment #3)
> yes, that's my understanding too. Currently only NFS supports recycling in
> production.

Thanks.  Closing.


Note You need to log in before you can comment on or make changes to this bug.