Skip to content

chore(deps): update terraform cloudposse/eks-node-group/aws to v3.3.0 #229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

public-glueops-renovatebot[bot]
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
cloudposse/eks-node-group/aws (source) module minor 3.1.1 -> 3.3.0

Release Notes

cloudposse/terraform-aws-eks-node-group (cloudposse/eks-node-group/aws)

v3.3.0

Compare Source

🚀 Enhancements

Include new AMI types AL2023_x86_64_(NVIDIA|NEURON) @​m-wynn (#​202)

what

  • Amazon has some new AMI types
    • AL2023_x86_64_NEURON
    • AL2023_x86_64_NVIDIA
  • These follow the same SSM parameters
    • /aws/service/eks/optimized-ami/1.31/amazon-linux-2023/x86_64/neuron/amazon-eks-node-al2023-x86_64-neuron-1.31-v20250103/image_id
    • /aws/service/eks/optimized-ami/1.31/amazon-linux-2023/x86_64/nvidia/amazon-eks-node-al2023-x86_64-nvidia-1.31-v20250103/image_id
    • /aws/service/eks/optimized-ami/1.31/amazon-linux-2023/x86_64/neuron/recommended/image_id
    • /aws/service/eks/optimized-ami/1.31/amazon-linux-2023/x86_64/nvidia/recommended/image_id

why

We want to be able to deploy all types of AMIs into our cluster for GPU and ML purposes. These are the AL2023 equivalents of AL2_x86_64_GPU

references

https://github.com/awslabs/amazon-eks-ami/releases
https://aws.amazon.com/blogs/containers/amazon-eks-optimized-amazon-linux-2023-accelerated-amis-now-available/

🐛 Bug Fixes

Bugfixes @​Nuru (#​205)

what

  • Fix use of var.kubernetes_version
  • Configure Terraform to create new node group before destroying old one when switching var.create_before_destroy from false to true
  • Revert code to be compatible with Terraform v1.3
  • Update test dependencies
  • Better tolerance of inputs from disabled EKS cluster module

why

  • Incorrectly treated list as scalar
  • Better user experience to implement create-before-destroy behavior when selecting that behavior
  • Version spec says module is compatible with Terraform 1.3
  • Keep current
  • Reduce special handling needed by client modules when setting enabled=false

references

v3.2.0

Compare Source

feat: Add support for enabling node-repair on worker nodes @​ChrisMcKee (#​203)

what

Adds support for node-repair feature in EKS

why

Its taken AWS years to add basic features to kill off nodes when kubelet dies

references


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@github-actions github-actions bot added the patch label May 4, 2025
Copy link

sonarqubecloud bot commented May 4, 2025

@public-glueops-renovatebot
Copy link
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants