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

Migrate Results from postgres 13 to 16

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      The default Tekton Results deployment uses a PostgreSQL image to setup a database required for its operation. With PostgreSQL version 13 being EOL as of November 13, 2025, we need to switch to the next supported version of 15 (version 14 was not productized). Tekton Results supports out of the box both versions, but the directory structure used by the PostgreSQL image changes between each version. Here we enable the automated transition from version 13 to version 15 which is part of the original PostgreSQL image. The transition uses the slower, but more reliable copy mechanism. If you are using the default PostgreSQL deployment ensure you have backed up your data and the underlying PVC has enough free space (more than 50% should be free) before you start the OpenShift Pipelines upgrade. If you are using external database with Tekton Results, you are not going to be affected by this change.
      Note: The default PostgreSQL deployment is only intended for preview and testing. For production deployments user should use external PostgreSQL compatible database and manage their own data (backups, etc.) and version upgrades.
      Show
      The default Tekton Results deployment uses a PostgreSQL image to setup a database required for its operation. With PostgreSQL version 13 being EOL as of November 13, 2025, we need to switch to the next supported version of 15 (version 14 was not productized). Tekton Results supports out of the box both versions, but the directory structure used by the PostgreSQL image changes between each version. Here we enable the automated transition from version 13 to version 15 which is part of the original PostgreSQL image. The transition uses the slower, but more reliable copy mechanism. If you are using the default PostgreSQL deployment ensure you have backed up your data and the underlying PVC has enough free space (more than 50% should be free) before you start the OpenShift Pipelines upgrade. If you are using external database with Tekton Results, you are not going to be affected by this change. Note: The default PostgreSQL deployment is only intended for preview and testing. For production deployments user should use external PostgreSQL compatible database and manage their own data (backups, etc.) and version upgrades.
    • Unspecified Release Note Type - Unknown
    • Pipelines Sprint CrookShank 42

      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

              enatan Emil Natan
              diagrawa Divyanshu Agrawal
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: