Story (Required)

As a Software Engineer, I want to optimize the processing time for Pipeline Runs involving large images in Tekton Chains

Background (Required)

In Konfluix, many build pipelines are blocked by chains finalizers, in some cases, for  over 6000 seconds. Consequently, PipelineRuns take a long time between completion and getting the chains sign annotation. 

it was observed that the problematic snapshots shared a common characteristic: they involved images with large scale, many of which exceeded 1GB in size. This suggests that the scale of images is likely contributing to the prolonged processing time.

Related to Konflux bug - https://issues.redhat.com/browse/KFLUXBUGS-24

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