Dear DevSecOps Team,
we would like to postpone the Kubernetes upgrade for our AKS unless there are compelling technical or operational reasons to proceed immediately. We prefer waiting until our current test phase is completed. This would allow us to carry out the upgrade in a
more controlled and low-risk manner.
Currently, Kubernetes version 1.33 is not supported by Azure, and no official release date has been announced. As such, the highest available version for upgrade is 1.32.
It is advisable to perform the upgrade first in the integration environment before rolling it out to the other stages. Since a direct upgrade is not possible, the cluster must be updated sequentially through several versions (1.29 → 1.30 → 1.31 → 1.32). This
process carries the risk of hitting the Docker pull rate limit, potentially leading to downtime. In such cases, the cluster would need to be shut down until the rate limit reset is reached.
Additional arguments in favor of postponement are the significant changes introduced between versions 1.30 and 1.32:
Identified risks:
* Removal of deprecated APIs (e.g. PodSecurityPolicy, batch/v1beta1), which could lead to service disruptions if still referenced in legacy deployments or custom resource definitions.
* Changes in the admission and scheduling logic (e.g. webhooks, PDBs) could cause unexpected side effects.
* Network changes (kube-proxy, DNS) that could impact production workloads if not thoroughly tested in advance.
Why a delay is currently justifiable:
* Our current version (v1.29.10) is fully supported by Azure Kubernetes Service and includes the latest security patches.
* While the new features in versions 1.30 through 1.32 (e.g., scheduler enhancements, container lifecycle hooks, debugging APIs) offer technical improvements, they are not critical for our current operational needs.
* Delaying the upgrade ensures we can validate compatibility in a non-critical environment and roll out changes more reliably across all stages.
Please let us know if there are considerations that would warrant a more urgent timeline.
Best regards,
DevOps on behalf of Catena-X Automotive Network e.V.
-----------------------------------------------------------------------------------------------------
Stefan Di Leo
Softwareentwickler
doubleSlash Net-Business GmbH
Otto-Lilienthal-Str. 16
D-88046 Friedrichshafen
Fon: +49 7541 / 70078-145
Fax: +49 7541 / 70078-111
Stefan.DiLeo@xxxxxxxxxxxxxx
http://doubleSlash.de
------------------------------------------------------------------------------------------------------
doubleSlash Net-Business GmbH
Geschäftsführung: Konrad Krafft, Andreas Strobel, Patrick Schmerbach
Sitz, Registergericht: Friedrichshafen, Amtsgericht Ulm HRB 631718
------------------------------------------------------------------------------------------------------
From: tractusx-dev on behalf of eclipse.tractusx--- via tractusx-dev
Sent: Thursday, April 24, 2025 03:35
To: tractusx-dev@xxxxxxxxxxx
Cc: eclipse.tractusx@xxxxxxxxx
Subject: [tractusx-dev] Action Required: Kubernetes New Release (1.33.0)
|
Sent from Outside of doubleSlash - be CAUTIOUS, particularly with links and attachments and with doing requested things (social engineering).
|
|
Absender außerhalb von doubleSlash - bitte VORSICHT beim Öffnen von Links und Anhängen sowie beim Ausführen angefragter Tätigkeiten (social engineering).
|
Kubernetes 1.33.0 Released!
|
Dear Tractus-X Community,
We're excited to inform you that Kubernetes has released a new version, 1.33.0, and we need your attention to ensure our projects remain up to date and secure. Please follow the instructions below.
Current Aligned Version:
Our projects are currently aligned to Kubernetes version 1.28.9.
Information of aligned Kubernetes versions can be found in the
TRG 5.10 - Kubernetes versions.
Upgrade process:
To guarantee a seamless integration with our infrastructure, we kindly request that you await the corresponding release for Azure Kubernetes before proceeding with any upgrades.
Once the Azure Kubernetes respective release is available, we recommend updating all existing clusters promptly. Furthermore, please review and adjust the versions of kind (Kubernetes in Docker) specified in your GitHub Actions workflows to maintain compatibility
and ensure optimal performance during the upgrade process.
Follow the
process to streamline documentation and communication alignment.
Resources
More information about latest release can be found on the official
Kubernetes website.
Contribution
We would like to invite you to contribute to this project and provide your valuable insights. Your feedback and suggestions will be greatly appreciated as we continue to refine and expand the functionality of our release notification tool.
To access the repository for this project and explore the code, please visit the following link:
sig-release/release-notifier.
Encourage you to visit general Tractus-X
How to Contribute guide.
We greatly appreciate your commitment to keeping our open source projects up-to-date and secure. Your collaboration is vital to the success of our community.
In the event of any issues with the release notification, please refer to the guide available at
Disabling and enabling a workflow for step by step instruction on disabling the GitHub Workflow.
If you encounter any issues or have questions during the upgrade process, please don't hesitate to reach out to
DevSecOps team.
Best regards,
DevSecOps Team
|
|