-
Notifications
You must be signed in to change notification settings - Fork 766
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
AWS Data Lifecycle Manager Support #2001
Comments
/kind feature |
@SimonBerens you can define a policy using AWS console or CLI that create snapshots of volumes that have a specific tag, then all EBS persistent volumes (existing and new) created with that tag in the same account and region will automatically be backed up based on the policy. So that you won't have to worry about volume IDs ahead of time. We've seen this is a common workflow for many customers. Would this work for your use case? If not, can you share more insight on your use case? |
This is a good workflow when defining tags at the StorageClass level. But it requires a dedicated StorageClass per tag to match the DLM policy. |
@ksliu58 Thanks that should work - then I should apply the tags via the storage class as documented in the Tagging docs, right? |
@SimonBerens Yes, you can follow the tagging doc you referenced if you want to associate a DLM policy with all volumes created by a StorageClass in a specific namespace. For example, if you have 3 DLM policies (one for prod, beta, and testing) and wanted to apply the respective DLM policy for all volumes created by a single StorageClass in the appropriate namespaces:
|
Please do let us know if this solved your use case, or if other aspects of DLM support are needed in the driver. |
Yes this solves our case, thank you! |
Is your feature request related to a problem? Please describe.
There doesn't seem to be an easy way to do automated backups with dynamically provisioned volumes. Specifically, there is no way to attach a dlm lifecycle policy to the volume as the volume handle is not known ahead of time.
Describe the solution you'd like in detail
Some sort of metadata/spec fields that I can add to my PVC to configure the DLM policy.
Describe alternatives you've considered
Jerryrigging something with kubernetes cron jobs.
The text was updated successfully, but these errors were encountered: