| [tractusx-dev] Action Required: Kubernetes New Release (1.29.1) |
Kubernetes 1.29.1 Released! |
|
Dear Tractus-X Community, We're excited to inform you that Kubernetes has released a new version, 1.29.1, 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.27.0. 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. ResourcesMore information about latest release can be found on the official Kubernetes website. ContributionWe 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 |