Global Retention Policies

[adambkaplan]

Feature Request

Define a global data retention policy feature for a Tekton Results. When enabled, a CronJob will regularly search for Results, Records, and Logs in storage and issue API calls to delete the data older than a specified duration.

Use Cases

• Prune data that is obsolete.
• See discussion in https://github.com/tektoncd/results/issues/221#issuecomment-1538685843

[khrm]

This and the pruner function provided by the operators are similar. @vdemeester

Is the operator the suitable place for this or the results? If it's latter, then we should provide a way to run this pruner without the storage capability of results.

[sayan-biswas]

@khrm Results already have pruning mechanism in the controller, this I guess is more targeted in deleting the data from the database and/or S3.

[adambkaplan]

this I guess is more targeted in deleting the data from the database and/or S3.

That is correct. And for this particular issue, the scope should be narrowed to a global, default retention for all Results records.

[adambkaplan]

Is the operator the suitable place for this or the results? If it's latter, then we should provide a way to run this pruner without the storage capability of results.

My inclination is Results - perhaps as a component in the config directory. @khrm - can you please clarify what you mean by "without the storage capability"?

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[adambkaplan]

/lifecycle frozen

This is something that should be considered on our long-term roadmap.

[khrm]

/assign @khrm