[konflux] set a finalizer so that PLR perists #1019
Draft
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.
Sometimes, during mass builds, a PipelineRun (PLR) might finish early but before our automation comes to check on it, it would have been pruned by konflux. Setting a finalizer will let us work around that.
But in order for us to be good citizens and don't put pressure on the etcd database by keeping a lot of PLRs around, we have to make sure to clean up after ourselves. Hence in addition to this, we would need a periodic job to remove our PLRs if the condition
.metadata.deletionTimestamp != null and .metadata.deletionTimestamp - now() > 12h
is satisfied.