Uploaded image for project: 'Agent-based Installer for OpenShift'
  1. Agent-based Installer for OpenShift
  2. AGENT-1184

OVE ISO build and release (TP - Ph1)

XMLWordPrintable

    • TP-OVE ISO build and release
    • False
    • False
    • Green
    • In Progress
    • OCPSTRAT-1985 - [Tech Preview - Ph 1] Agent Installer for OpenShift Virtualization
    • OCPSTRAT-1985[Tech Preview - Ph 1] Agent Installer for OpenShift Virtualization
    • 4% To Do, 0% In Progress, 96% Done
    • L
    • Hide

      12-18-2025: Green Text
      An agent ISO based on OCP 4.20.8 has been pushed the CGW and is available here https://mirror.openshift.com/pub/cgw/assisted-installer-disconnected/4.20.8/.

      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.
      Show
      12-18-2025: Green Text An agent ISO based on OCP 4.20.8 has been pushed the CGW and is available here https://mirror.openshift.com/pub/cgw/assisted-installer-disconnected/4.20.8/ . 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.

      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)

      1. 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>

              bfournie@redhat.com Robert Fournier
              afasano@redhat.com Andrea Fasano
              pawan pinjarkar
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: