Story (Required)

Make Results use Server-Side apply for managing finalizers in a more efficient way. The original story scope (below) + some extras are going to be managed under the #srvkp-8169 Epic.

The issue surfaced after we removed the (old) Tekton pruner from the Konflux production clusters. The cluster etcd database hit its limit because pipelineruns and the respective taskruns and pods were not pruned. Generally this should be responsibility of the Tekton Results pruner, but in a few cases I checked, there were multiple finalizers on the pipelinerun including the PaC, Chains and Results finalizers. Those three have their own logic about their respective finalizers and yet all 3 of them were left for hours after the pipelinerun has completed.
For the time being, the Tekton pruner was re-enabled to prevent the etcd overload.

Slack thread: https://redhat-internal.slack.com/archives/C080ZT4KGFK/p1747827036038659

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met