PURIS – Upgrade to PostgreSQL 17.x

[ds-hzimmer]

Description

Goal: Upgrade PURIS to use PostgreSQL 17.x in order to harmonize all Tractus-X products to a common and long-term-supported PostgreSQL major-release version. This ensures support through the expected operative lifetime of Tractus-X 25.12 respectively Catena-X "Saturn" and "Titan" releases.

See main issue eclipse-tractusx/sig-release#1501 for further details.
The applicable TRG 5.07 - Chart Dependencies will also be updated.

Test and Release Management will coordinate this activity.

Why it matters

• Ensures long support window for used database version (PostgreSQL 17.x support currently scheduled until November 2029)
• PostgreSQL performance, efficiency, and security improvements included in this release
• Potentially reduces upgrade risks/efforts when having to make an upgrade "jump" by several major PostgreSQL versions in the future.
• Better harmonizes the supported PostgreSQL (major) version across all Tractus-X products for a release.

Acceptance Criteria

1. Upgrade database configuration to PostgreSQL 17.x
   (Note: Currently the latest stable minor version is 17.5 but this may change during release phase. Version 18.x is currently not yet a stable release version).
2. Successfully run all regression and integration tests of your product's release candidate using the new DB version in the milestone release test phase to ensure expected functionality and performance are in line with the version you upgraded from.

If upgrade cannot be completed within the intended 25.12 release due to time/effort/identified fu

Overview

Explain the topic in 2 sentences

Upgrade PURIS to use PostgreSQL 17.x in order to harmonize all Tractus-X products to a common and long-term-supported PostgreSQL major-release version. This ensures support through the expected operative lifetime of Tractus-X 25.12 respectively Catena-X "Saturn" and "Titan" releases.

What's the benefit?

• Ensures long support window for used database version (PostgreSQL 17.x support currently scheduled until November 2029)
• PostgreSQL performance, efficiency, and security improvements included in this release
• Potentially reduces upgrade risks/efforts when having to make an upgrade "jump" by several major PostgreSQL versions in the future.
• Better harmonizes the supported PostgreSQL (major) version across all Tractus-X products for a release.

What are the Risks/Dependencies ?

• leapfrogging to 17.x from 15.x may be unhandy.
• how to handle bitnami license update?

Detailed explanation

Upgrade PURIS to use PostgreSQL 17.x in order to harmonize all Tractus-X products to a common and long-term-supported PostgreSQL major-release version. This ensures support through the expected operative lifetime of Tractus-X 25.12 respectively Catena-X "Saturn" and "Titan" releases.

See main issue eclipse-tractusx/sig-release#1501 for further details.
The applicable TRG 5.07 - Chart Dependencies will also be updated.

Test and Release Management will coordinate this activity.

Current implementation

15.x appVersion bitnami chart

Proposed improvements

17.x appVersion bitnami chart

Feature Team

Contributor

• @ReneSchroederLJ
• @OlgaIvkovic

Committer

• @tom-rm-meyer-ISST

User Stories

Likely just this one covering:

• local deployment
• helm chart
• postgresql dependencies
• migration guide

Acceptance Criteria

• Upgrade database configuration to PostgreSQL 17.x
  (Note: Currently the latest stable minor version is 17.5 but this may change during release phase. Version 18.x is currently not yet a stable release version).
• Successfully run all regression and integration tests of your product's release candidate using the new DB version in the milestone release test phase to ensure expected functionality and performance are in line with the version you upgraded from.

If upgrade cannot be completed within the intended 25.12 release due to time/effort/identified fu

Test Cases

TBD

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented.

In the context of the standards 126 and 127, typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.

• This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
    • CX-0010 Business Partner Number
    • CX-0013 Identity of Member Companies
    • CX-0018 Data Space Connectivity (EDC)
    • [ ] CX-0049 DID Document Schema
    • CX-0050 Framework Agreement Credential
    • CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • CX-0001 EDC Discovery API
    • CX-0002 Digital Twins in Catena-X
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0126 Industry Core: Part Type 2.0.0
    • [ ] CX-0127 Industry Core: Part Instance 2.0.0
  • Data Format:
    • The data model is based on a published Semantic Model
• The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)

[tom-rm-meyer-ISST]

Thanks for providing the feature. We're going to try to do the jump to 17.x. If we encounter issues, we might only go for 16.x first.

Also we will need to align during committer round / office hour for a harmonized version - I consider 17.x as this considered harmonized version, right?

[tom-rm-meyer-ISST]

@ds-hzimmer I migrated your feature to the sig-release feature template. Just wanted to mention so that you're not confused during revisit! :)

[ds-sdileo]

Hi @tom-rm-meyer-ISST, I see the task is in your backlog. I just wanted to check if it is still planned for the next release 25.12?