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