Upgrade Kubernetes Versions to Latest (1.29.x) Across All Cloud Providers

[strickvl]

In our current MLStacks terraform definitions, the Kubernetes cluster versions are specified as being 1.22 for AWS, 1.25 for GCP, and 1.24.4 for k3d. These versions are now behind the latest Kubernetes release, which is 1.29.x. Upgrading to the latest version will ensure compatibility with new Kubernetes features and improvements.

Task Description

Upgrade the specified Kubernetes versions in the MLStacks terraform definitions to the latest version (1.29.x). This upgrade should be performed individually for each cloud provider (AWS, GCP, and k3d), with thorough testing conducted to ensure that all components function correctly with the new Kubernetes version. Attention should be paid to other components that may require updates or modifications following the Kubernetes version upgrade.

Expected Outcome

• Kubernetes cluster versions in MLStacks terraform definitions for AWS, GCP, and k3d are updated to 1.29.x.
• Comprehensive testing is performed for each cloud provider to confirm that MLStacks operates seamlessly with the upgraded Kubernetes version.
• Any necessary adjustments to other components are identified and implemented to maintain compatibility and functionality.

Steps to Implement

1. Update the Kubernetes version in the terraform definitions for AWS, GCP, and k3d to 1.29.x.
   • AWS: src/mlstacks/terraform/aws-modular/locals.tf
   • GCP: src/mlstacks/terraform/gcp-modular/locals.tf
   • k3d: src/mlstacks/terraform/k3d-modular/locals.tf
2. Conduct thorough testing on each cloud provider using the new Kubernetes version to ensure all functionalities and components work as expected.
3. Monitor for any errors or compatibility issues that arise from the version upgrade and address them by updating or modifying other components as needed.
4. Document any changes made during the upgrade process, including adjustments to other components, to serve as a reference for future upgrades and maintenance.

Additional Context

Staying updated with the latest Kubernetes versions is crucial for leveraging new features and improvements while ensuring the security and reliability of our MLStacks deployments. This upgrade process also presents an opportunity to review and refresh our terraform definitions and dependencies.

Code of Conduct

• I agree to follow this project's Code of Conduct

[vu-eric]

Hello, I’d like work on this task.

[JoshuaWLindsay]

Hey @strickvl, could you please assign me to this task?