Story (Required)

As a Konflux maintainer, I am restricted in the amount of information that can be stored in the results of Tekton Tasks. This impacts my ability to fulfill certain requirements.

Background (Required)

One of our Tasks, buildah stores as a result base images used in the build. If the Dockerfile uses too many unique base images, i.e. FROM statements, then the whole Pipeline fails. On the same Task, we have also tried to add a new result from the SBOM URL, but had to revert the change because this pushed some users over the 4k limit.

Out of scope

This is an early feature and requires significant evaluation before being deployed to production. Production deployment, if deemed safe/reasonable, should be done in a follow up issue.

Approach (Required)

Evaluate if using sidecar logs is a viable option, then attempt the changes in Konflux staging.

PLNSRVCE-1514 was meant as an attempt to enable the feature. However, the attempt was not successful for multiple reasons:

1. No testing was done before deploying to staging.
2. Docs were not followed to grant get access to all pod/logs resources as suggested in the docs.

Let's make sure we don't make the same mistakes here.

Dependencies

None

Acceptance Criteria (Mandatory)

• A decision is made on whether or not sidecar logs should be used as a solution to allowing larger results in Tekton Tasks.

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