Open adambkaplan opened 1 year ago
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.
/lifecycle frozen
This is something we should keep on the roadmap.
/area roadmap
This should be implemented in the feature flag way because there are use-cases where we want to access logs/metadata when a namespace is deleted.
This should be implemented in the feature flag way because there are use-cases where we want to access logs/metadata when a namespace is deleted.
Something to verify is if SAR checks work if the namespace is deleted, but the user accessing the record has cluster-scoped permission to view the data in Results.
Feature request
When a namespace is deleted, ensure that all Results data related to that namespace is deleted.
Use case
Note that our authz checks rely on namespace-scoped SAR checks - if a namespace is deleted, only users with elevated permissions may access Results data.