feat: update EKS and addon versions so that we can go from 1.28 -> 1.29 upgrade

[venkatamutyala]

[…](feat: update EKS and addon versions so that we can go from 1.28 -> 1.29 upgrade)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Version Compatibility Ensure that the updated EKS version (1.29) is compatible with the specified CoreDNS and Kube Proxy versions. Verify that these versions are recommended and supported together. Default Version Update Confirm that the new default versions for CoreDNS and Kube Proxy are the latest stable versions recommended for EKS 1.29. Check AWS documentation for any potential issues or recommendations. Documentation Update Verify that all references to EKS, CoreDNS, and Kube Proxy versions in the README have been updated consistently. Ensure the documentation accurately reflects the new versions and any changes in configuration.

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Enhancement	Update the default EKS version in variables to match the new configuration Update the default value of the eks_version variable to match the new version (1.29) used in the configuration. This ensures consistency and prevents potential version mismatch issues. variables.tf [200] variable "eks_version" { type = string - default = "1.27" + default = "1.29" description = "The version of EKS to deploy" } Apply this suggestion Suggestion importance[1-10]: 9 Why: Updating the default EKS version in the variables file to match the new configuration is crucial for consistency and prevents potential version mismatch issues. This change directly aligns with the updates made in the PR, ensuring the configuration is coherent and functional.	9
Best practice	Update commented node pool configurations to match new Kubernetes and AMI versions Consider updating the commented-out node pool configurations to match the new Kubernetes version and AMI release version. This ensures consistency across the configuration and prevents potential issues if these commented sections are uncommented in the future. tests/main.tf [11-18] +# { +# "kubernetes_version" : "1.29", +# "ami_release_version" : "1.29.8-20241024", +# "ami_type" : "AL2_x86_64", +# "instance_type" : "t3a.large", +# "name" : "glueops-platform-node-pool-1", +# "node_count" : 4, - Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion to update the commented-out node pool configurations ensures consistency and prevents potential issues if these sections are uncommented in the future. It aligns the configuration with the new Kubernetes and AMI versions, which is a good practice for maintainability.	7

💡 Need additional feedback ? start a PR chat