Story (Required)

So, we have a component tekton-cache component, which is distributed as an OCI image right now and is consumed as steps (StepActions).
There was a recent use case with one of the customers where they raised an requirement to use it but as a binary and not the StepActions.
They wish to bake images they called Universal, and the want to have the tekton-cache binary in there instead of rely of the StepAction. For that reason, they need a way to get the red hat supported binary which would allow them to achieve their need

Approach (Required)
**

There is two options :

• publish the tekton-cache in a public repository (in registry.redhat.io) so that they can pull it "anonymously"

• packages it with opc

• publish the binary alongside tkn and opc in mirror.openshift.io

<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