-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
No LifeCycle Policy in Repository #4363
Comments
There is no such thing at the moment no. You can set up a lifecycle policy in S3 though, be careful so the deleted data don't break the integrity of the image graph! |
@milosgajdos Thanks for your quick response. I see that you've mentioned the S3 lifecycle policies here. I agree that these could be done but I am unsure how to setup a proper lifecycle policy for the same.. I mean I don't know which files should I delete and which to retain? Can you help me out on that please? Thanks. |
This is a complicated problem @dextercrypt ...you need to make sure you won't break the integrity of the content stored in registry so the S3 lifecycle policy can really help maybe with purging broken uploads but I'd not use it for the use case you're after. We've no plans to implement this at the moment, but feel free to take a stab at it! |
Hi @milosgajdos, Okay I understood the issue. I might look at it further but at this moment do you know how can I set this up or you know someone who managed to do this? The reason I am afraid to put a lifecycle on this is that once it breaks the Layer files of the Registry, I fear that my registry would get corrupted or something and I might lose my data. Is there any way you can help? |
Yes, that's the right worry...as I said:
No, I don't know anyone I'm afraid. And as I said, I'd be wary about implementing it in S3...lifecycle policies in S3 are handy for purging failed uploads though. But not useful at all for application-aware stores. |
Description
Hi,
I have seen that we do not have Lifecycle policy feature in the registry? I want to delete some old images and tags from my Repository as they are on S3 storage and it's spiking up the bills.
Can anyone tell me how to do it? Or do we have any feature for this?
Can we implement a Lifecycle Policy Feature?
Thanks.
The text was updated successfully, but these errors were encountered: