Re: [tractusx-dev] Aligning Tractus-X Contributors on Kubernetes and Pos

["Meyer, Tom" <tom.meyer@xxxxxxxxxxxxxxxxxx>]

Hey Siggi & mailing list,

 

I really do appreciate the governance! As we already define a few versions in the TRGs, we should reflect the changes the respective TRGs

• TRG 5.07 (Helm chart dependency versions) for postgresql
• TRG 5.10 for Kubernetes

 

From my point of view, we have another topic to address in TRG 5.07. I checked a few repositories and no repo defines the EDC as a dependency. I guess especially the tractus-x connector is an interesting dependency because

• The authentication and protocol changed in the recent month, it makes sense to define the compatible / dependent version BUT
• One could use another connector / EDC bundle and it’s hard to define the respective dependencies

 

Another question would be, if the Tractus-X needs to be enhanced to make the current “dataspace infrastructure” (e.g., MIW, Connector, Portal) visible, too. Either each operating company OR the Tractus-X should guide adopters regarding these dependencies.

 

Thanks in advance.

 

Tom Meyer

Fraunhofer-Institut für Software- und Systemtechnik ISST

Wissenschaftlicher Mitarbeiter Logistik

Speicherstraße 6, 44147 Dortmund, Germany

Telefon +49 231 97677-442

tom.meyer@xxxxxxxxxxxxxxxxxx
www.isst.fraunhofer.de

 

--------------------------------------------------------------------------------------------------

 

Folgen Sie uns: 

 

       

 

 

 

From: tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> On Behalf Of Kiermayer, Siegfried via tractusx-dev
Sent: Monday, 11 September 2023 10:56
To: tractusx-dev@xxxxxxxxxxx
Cc: Kiermayer, Siegfried <siegfried.kiermayer@xxxxxxx>
Subject: [tractusx-dev] Aligning Tractus-X Contributors on Kubernetes and PostgreSQL Versions for Upcoming Development

 

Dear Tractus-X Project Contributors,

 

I hope all is well with you. As our project evolves, it becomes increasingly important for us to maintain a streamlined operational environment. To achieve this, I'd like to guide us toward aligning on specific versions of Kubernetes and PostgreSQL across all development and production scenarios.

 

🚀 Kubernetes Version Alignment

Our production environment is hosted on Azure Kubernetes Service (AKS), which currently supports Kubernetes version 1.26. Accordingly, it would be beneficial for all of us to ensure our developments are compatible with Kubernetes version 1.26.

 

Additionally, to maintain forward compatibility, your Helm tests need to also include support for Kubernetes versions 1.27 and 1.28. You can find more details on these versions on the official Kubernetes Releases page.

 

🗄️ PostgreSQL Version Upgrade

For the sake of operational simplicity in real production environments, it's important that we standardize on a single PostgreSQL version. I suggest that we align on PostgreSQL version 15.4. Achieving this alignment will aid in maintaining a consistent and efficient operational posture.

 

To make the upgrade process easier, you can update your Bitnami chart to version 12.11.1, as specified in the Bitnami GitHub repository: Bitnami PostgreSQL Chart.

 

Here's a Wikipedia page on PostgreSQL for their versioning strategy: PostgreSQL Wikipedia.

 

📋 Summary

• Align on PostgreSQL version 15.4 for operational simplicity across all Helm charts
• Ensure developments are compatible with Kubernetes version 1.26 (while also supporting 1.28 and 1.27 in Helm tests)

 

Your attention to these details is greatly appreciated 👍. Aligning on these versions will help us avoid any operational inconsistencies and enable smoother deployments moving forward.

 

If you have any questions or need further clarification, please don't hesitate to reach out.

 

Thank you for your continued commitment to the Tractus-X project.

 

Best regards,

 

Sigi Kiermayer

Tractus-X Eclipse Project Lead