feat: introduce retention policy support #3709
Draft
+2,936
−83
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shreddedbacon
force-pushed
the
retention-policies
branch
from
ac1111f to
27c10b4
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
from
27c10b4 to
7d58364
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
from
7d58364 to
6b70b89
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
from
6b70b89 to
ad20e12
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
2 times, most recently
from
cdd16b5 to
641862f
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
2 times, most recently
from
ebca482 to
d4fd21a
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
3 times, most recently
from
8949ac1 to
0d9b7cb
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
2 times, most recently
from
5916484 to
d2cbcf4
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
from
d2cbcf4 to
1cbb40d
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
from
1cbb40d to
f5c6943
Compare
shreddedbacon
force-pushed
the
retention-policies
branch
from
ae17097 to
41b5925
Compare
…backup and storage history
…ale data when removed
shreddedbacon
force-pushed
the
retention-policies
branch
from
41b5925 to
9c35fd8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
General Checklist
Database Migrations
Introducing retention policy support to Lagoon. This first iteration only contains Harbor and history based retention policy support.
Retention policy support allows platform owners to configure policies globally, organizationally, or directly on projects. Policy inheritance exists-ish, and a project will override organization, which will override global.
Harbor Policies
Harbor policies allow for retaining the Last Pulled number of images based on rules that can be defined. This allows platform owners to be able to write rules that could retain all images of a project for the last # pulled images. Or configure multiple rules based on doublestar pattern matching that Harbor uses to prune some images more aggressively than others.
Harbor policies are enforced when they are linked, unlinked, updated, or when a deployment reaches the final stages. It uses hooks on certain events, and then send messages to the remotes to inform their configured Harbor of any policy changes that are required.
This requires that the
remote-controllerbe updated with support for receiving the retention policy payloadsHistory Policies
History policies allow for retaining the last X number of builds and tasks and associated files/logs for these. It is possible to configure this for
COUNT,DAYS,MONTHS. This allows for platform owners to retain a small number of builds and tasks within an environment if they choose to.History policies are enforced whenever a new task or build is created.
See the README for more information about retention policies.