[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: AWS EBS and PV Reclaim Policy Question



So would best practice at this time be to just backup the EBS volumes backing the metrics(Cassandra),logging(elasticsearch), and any other dynamically created pv (Jenkins, etc..) ? . Is there a process to better than I described to change the reclaim policy to retain from the default of delete?  Am I understanding correctly that at this time, there is no way to change the default setting of ‘delete’ on AWS EBS dynamically created pv?

 

Thank you

 

Todd

 

From: Hemant Kumar <hekumar redhat com>
Date: Wednesday, November 29, 2017 at 11:36 AM
To: "Walters, Todd" <Todd_Walters unigroup com>
Cc: "users lists openshift redhat com" <users lists openshift redhat com>
Subject: Re: AWS EBS and PV Reclaim Policy Question

 

Hello Todd,

 

Reclaim policy is unfortunately not configurable via StorageClass in Openshift-3.6. You will have to wait for 3.8 release to be able to use configurable reclaim policy.  I am not aware of any workaround that is available for it. 

 

 

 

On Wed, Nov 29, 2017 at 12:28 PM, Walters, Todd <Todd_Walters unigroup com> wrote:

Hello Hemant,

I was able to define my storageclass to change default to type ‘encrytped’ but anytime I tried to add the reclaim policy as default ‘retain’ at the storage class level it failed to work properly.

 

My current sc file

 

apiVersion: storage.k8s.io/v1

kind: StorageClass

metadata:

  annotations:

    storageclass.beta.kubernetes.io/is-default-class: "true"

  creationTimestamp: 2017-11-20T15:17:33Z

  name: gp2-encrypted

  resourceVersion: "444871"

  selfLink: /apis/storage.k8s.io/v1/storageclasses/gp2-encrypted

  uid: ef0a4237-ce05-11e7-890f-0e8b400c9cda

parameters:

  encrypted: "true"

  kmsKeyId: xxxxxxxxxxxxxxxxxxxxxx

 type: gp2

 

ideally I’d like the pv to be dynamically created with the retain policy by default. It’s not convenient to have our developers request a pv, (get ebs vol id first) then create pv.yml with that set to retain.  And the logging and metrics dynamically creates the pv during install so they are ‘delete’ reclaim policy too.  I have to manually delete the pvc, recreate with policy retain’ to have those stay.

 

Is there a current work around, that is not manual, to dynamically provision pv with retain reclaimpolicy?

 

Thanks,

 

Todd

 

 

From: Hemant Kumar <hekumar redhat com>
Date: Wednesday, November 29, 2017 at 11:11 AM
To: "Walters, Todd" <Todd_Walters unigroup com>
Cc: "users lists openshift redhat com" <users lists openshift redhat com>
Subject: Re: AWS EBS and PV Reclaim Policy Question

 

I suppose you are currently using dynamic provisioning and want to configure reclaim policy via storageClass for all dyanmically created PVs?

 

We just had this feature merged in Openshift-3.8 branch where you can configure reclaim policy of all dynamically created PVs. This feature however isn't available in 3.6.  We haven't considered backporting the feature back to 3.6 because it involves API change.

 

 

 

 

 

On Wed, Nov 29, 2017 at 11:57 AM, Walters, Todd <Todd_Walters unigroup com> wrote:

We have aws and openshift origin cluster working well and using EBS for storage for pv’s.  I would like to set the default reclaim policy to ‘retain’ but have not figured out how to set that in my playbooks?

 

Does anyone know how to change the default  persistentVolumeReclaimPolicy from ‘delete’ to ‘retain’?

My other option I could use is create the EBS volume manually and then create the pv-manual.yml file to point to that Vol ID and set the  persistentVolumeReclaimPolicy. But this is not ideal.

 

I’d also like to set this pv reclaim policy to ‘retain’ for our logging and metrics persistent storage but have not found setting for this in playbooks. We’re on v.3.6.

 

Thank you,

 

Todd Walters

Todd_Walters unigroup com


########################################################################
The information contained in this message, and any attachments thereto,
is intended solely for the use of the addressee(s) and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination, copying, or other use of the transmitted information is
prohibited. If you received this in error, please contact the sender
and delete the material from any computer. UNIGROUP.COM
########################################################################


_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

 


########################################################################
The information contained in this message, and any attachments thereto,
is intended solely for the use of the addressee(s) and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination, copying, or other use of the transmitted information is
prohibited. If you received this in error, please contact the sender
and delete the material from any computer. UNIGROUP.COM
########################################################################

 


########################################################################
The information contained in this message, and any attachments thereto,
is intended solely for the use of the addressee(s) and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination, copying, or other use of the transmitted information is
prohibited. If you received this in error, please contact the sender
and delete the material from any computer. UNIGROUP.COM
########################################################################


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]