-
Notifications
You must be signed in to change notification settings - Fork 21
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
Introduce v1alpha3 and make the garbage collection TTL configurable #144
Introduce v1alpha3 and make the garbage collection TTL configurable #144
Conversation
/hold |
0f10438
to
ab3f00d
Compare
/hold cancel |
ab3f00d
to
b0ee794
Compare
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.
/lgtm
LGTM label has been added. Git tree hash: 9504debe6e2bc9deb67db1f54d72c8b24c5587a1
|
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.
/lgtm
LGTM label has been added. Git tree hash: e83ff2c2d7535722df396a42d59538dd2c7cb43f
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dimitar-kostadinov The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
How to categorize this PR?
/kind enhancement
What this PR does / why we need it:
This PR introduces v1alpha3 to make the garbage collection TTL configurable. With #138 we upgraded to v3.0.0-alpha.1 of distribution/distribution. In that version the proxy's garbage collection TTL is configurable. In prior versions it was hard-coded to
168h
(7 days). Making the TTL configurable is needed to increase registry-cache's efficiency. Otherwise, every blob expires and gets deleted in 7 days, then it has to pulled again.Q: Why we need to introduce v1alpha3 to make the TTL configurable?
A: v1alpha3 replaces the current
garbageCollection.enabled
field withgarbageCollection.ttl
. We were so far abusing with thestorage.delete.enabled
config option of the Distribution project to control garbage collection. With the ttl field, the GC can be natively disabled by setting ttl=0. Having only the ttl field also keeps the API simple and in sync with what the Distribution project exposes as config options for the proxy.Which issue(s) this PR fixes:
Part of #3
Special notes for your reviewer:
N/A
Release note: