XML

Word

Printable

Type: Epic
Resolution: Unresolved
Priority: Blocker
Fix Version/s: openshift-4.20
Affects Version/s: None
Component/s: Installer / Agent based Installer
Labels:
- no_core_payload

Epic Name:
TP-OVE ISO build and release
Blocked:
False
Ready:
False
Color Status:
Yellow
Epic Status:
In Progress
Feature Link:
OCPSTRAT-1985 - [Tech Preview - Ph 1] Agent Installer for OpenShift Virtualization
Parent Link:
OCPSTRAT-1985[Tech Preview - Ph 1] Agent Installer for OpenShift Virtualization
Hierarchy Progress Bar:

8% To Do, 8% In Progress, 83% Done
Size:
L
Status Summary:
Hide

11-05-2025: Yellow

The MR https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/11025 defining the ReleasePlan and ContractPolicy has merged. The next steps are to define any operator version changes that are needed for 4.20 and wait for all of the operators to be available in the catalog. When that happens we will create Release CR to push the ISO to registry.redhat.io. The pipeline that is being used - rh-push-to-registry-redhat-io - will not create an official advisory for the release.

10-29-2025: Yellow

Working with the Konflux and CLOUDDST teams, there has been another change to the recommended pipeline, now *rh-push-to-registry-redhat-io *is the one that is recommended. This will not generate an official public advisory. The ISO will not be in the Container Catalog, it will be in the registry.redhat.io, but won't be visible at all at the RHEC. Once the *push-artifacts-to-cdn *pipeline is available for 4.21 we can switch to that for the same effect.
At this point we are waiting for https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/11025 containing the ReleasePlanAdmission with the above pipeline to be approved. it is passing all of the tests.
Show
11-05-2025: Yellow The MR https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/11025 defining the ReleasePlan and ContractPolicy has merged. The next steps are to define any operator version changes that are needed for 4.20 and wait for all of the operators to be available in the catalog. When that happens we will create Release CR to push the ISO to registry.redhat.io. The pipeline that is being used - rh-push-to-registry-redhat-io - will not create an official advisory for the release. 10-29-2025: Yellow Working with the Konflux and CLOUDDST teams, there has been another change to the recommended pipeline, now *rh-push-to-registry-redhat-io *is the one that is recommended. This will not generate an official public advisory. The ISO will not be in the Container Catalog, it will be in the registry.redhat.io, but won't be visible at all at the RHEC. Once the *push-artifacts-to-cdn *pipeline is available for 4.21 we can switch to that for the same effect. At this point we are waiting for https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/11025 containing the ReleasePlanAdmission with the above pipeline to be approved. it is passing all of the tests.

Target Version:

openshift-4.20

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

Intelligence Requested:
Market:

Epic Goal

Setup an enterprise-grade build and release pipeline for the 4.20 TP OVE ISO artifact

Why is this important?

The OVE ISO will have to be released automatically for each z-stream ocp release, in order to allow any customer to use it as any other ocp release

Acceptance Criteria

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

The release pipeline will need to be discussed and agreed with the CLOUDDST team

Open questions::

Done Checklist

CI - CI is running, tests are automated and merged.
Release Enablement <link to Feature Enablement Presentation>
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Polarion: <link or reference to Polarion>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>