Epic Goal

• Ensure the upstream Tekton work to enable podTemplate in TaskRunSpecs in a PipelineRun is pulled into Shipwright and anything else needed to enable this feature is completed

Why is this important?

• This is important to Shipwright since they can make use of the features in https://issues.redhat.com/browse/MULTIARCH-5313 

Scenarios
1. …

Acceptance Criteria

• A plan for ensuring Shipwright can inherit these features is investigated
• The base features of https://issues.redhat.com/browse/MULTIARCH-5313 are enabled in Shipwright
• Additional features, if identified as helpful, are developed in Shipwright

Dependencies (internal and external)
1. BUILD team

Previous Work (Optional):
1. …

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.