Epic Goal

Onboard s2i to Konflux so we can build and release an s2i container image, based on v1.4.0

Why is this important?

• s2i is used in many Red Hat products, such as OpenShift Pipelines, Builds for OpenShift, and OpenShift AI
• CPaaS is deprecated as a downstream build system.

Scenarios

1. Build containers with latest s2i release in a Tekton pipeline
2. Build containers with latest s2i in a Shipwright build

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Release s2i container image via Konflux for at least one architecture (x86)

Dependencies (internal and external)

TBD

Previous Work (Optional):

N/A

Open questions::

1. Must we support multi-arch images? Out of scope for this epic - requires KONFLUX-387

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment