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

Test and update Tekton Results with Postgres version 16/17

XMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • Tekton Results PostgreSQL database version upgraded to 17.5.
    • Enhancement
    • Proposed
    • Pipelines Sprint Tekshift 32

      Story (Required)

      A customer (Konflux) is using Results with RDS instance of DB hosted on AWS. The version currently in use is version 13. It's EOL and the customer must switch to a newer version - 16 or 17.
      Verify that Tekton Results supports Postgres version 17.

      Version 13 is still supported, it will reach end of standard support on February 28, 2026
      We need to move before this date if we do not want pricing to go up as 13 will fall under RDS with extended support on that day

      If the transition does not require any changes, update the upstream project to use newer version in the CI.

      (If work is required and it is estimated to more that few hours, this could be handled in a separate ticket.)

      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>

      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

          There are no Sub-Tasks for this issue.

              rh-ee-abghosh Abhishek Ghosh
              enatan Emil Natan
              Sri Vignesh Selvan Sri Vignesh Selvan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: