Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1136

Switch to UBI 8 Base Images

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • s2i-1.4
    • s2i-1.4
    • s2i
    • None
    • 1
    • False
    • None
    • False
    • KFLUXMIG-303 - Source-to-Image enablement
    • Release Note Not Required
    • Proposed
    • Builds Sprint #13
    • 1

      Story (Required)

      As a Red Hat engineer trying to release s2i I want the image based on UBI 8

      <Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

      Background (Required)

      <Describes the context or background related to this story>

      The initial onboarding for s2i on Konflux was based on UBI9 images. These should be switched to ubi8 in the interim so we do not need to create new entries in Comet, and customers can easily upgrade.

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Change base images from ubi9 (go-toolset, ubi-minimal) to ubi8, with respective updates to the tagged version

      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

              rh-ee-sabiswas Sayan Biswas
              adkaplan@redhat.com Adam Kaplan
              Adam Kaplan Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: