Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-9337

Migrate Hub from postgres 13 to 16

XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Tekton Hub database deployment uses a PostgreSQL version 13 image which is going to be EOL as of November 13, 2025, we need to switch to the next supported version of 15 (version 14 was not productized). Here we enable the automated transition from version 13 to version 15.
      Show
      Tekton Hub database deployment uses a PostgreSQL version 13 image which is going to be EOL as of November 13, 2025, we need to switch to the next supported version of 15 (version 14 was not productized). Here we enable the automated transition from version 13 to version 15.
    • Unspecified Release Note Type - Unknown
    • Proposed
    • Pipelines Sprint CrookShank 42, Pipelines Sprint CrookShank 43

      Story (Required)

       

      As postgres 13 is going to be EOL so we need to migrate to postgres 16

      As a <PERSONA> trying to <ACTION> I want <THIS OUTCOME>

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

      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>

      • Migrate from postgres 13 to postgres16
      • Create a doc for the migration

      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

              shverma Shiv Verma
              diagrawa Divyanshu Agrawal
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: