results icon indicating copy to clipboard operation
results copied to clipboard

Retention Policies for Results

Open adambkaplan opened this issue 2 years ago • 8 comments

Feature request

Allow Tekton Results to define retention policies for parent results and their associated child records. These retention policies could be defined for the entire cluster, with overrides for specific namespaces.

Use case

  • Data retention compliance.
  • Data retention flexibility in multi-tenant environments. If namespaces are used to define tenancy, some namespaces may want results data retained for small periods of time, while others may need data retained long term/permanently.

adambkaplan avatar Aug 22 '22 19:08 adambkaplan

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.

tekton-robot avatar Nov 20 '22 20:11 tekton-robot

/remove-lifecycle stale

This is still a valid concern.

adambkaplan avatar Nov 22 '22 15:11 adambkaplan

/area roadmap

vdemeester avatar Feb 15 '23 15:02 vdemeester

Would be great to have a cleanup job in the api which would cleanup results and its children records if older than a certain period of time. Maybe we can implement a first version without multi tenant support?

manuelwallrapp avatar Apr 28 '23 12:04 manuelwallrapp

/lifecycle frozen

I agree that having a "v1" that applies to the whole installation makes a lot of sense. I will ~~mark namespace-level features as out of scope so it is easier for contributors to get started~~ create a new issue to capture the global retention policy feature.

adambkaplan avatar May 08 '23 16:05 adambkaplan

/assign @khrm

khrm avatar Jul 18 '24 09:07 khrm

Would be great to have a cleanup job in the api which would cleanup results and its children records if older than a certain period of time. Maybe we can implement a first version without multi tenant support?

Yes. First,we would implement this and then we are going with filters.

khrm avatar Jul 18 '24 09:07 khrm

We would appreciate this feature very much! Thank you!

manuelwallrapp avatar Jul 18 '24 10:07 manuelwallrapp