Skip to content
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

desired_size on eks node-group shouldn't be ignored during the lifecycle of an aws_eks_node_group #1879

Closed
DanMaxic opened this issue Feb 15, 2022 · 8 comments

Comments

@DanMaxic
Copy link

desired_size on eks node-group shouldn't be ignored during the lifecycle of an aws_eks_node_group

@bryantbiggs
Copy link
Member

it is a deliberate design decision in order to support the predominant use of scaling services like cluster autoscaler, Karpenter, etc.

@llacoste
Copy link

This creates a problem if you are not using any form of autoscaling. For example, my cluster has 3, 6, and 9 for the values of min, desired, and max respectively. I am adjusting the terraform in order to double my clusters capacity. Now I am getting an error that the minimum cannot be larger than desired when using this module.

I believe as a workaround I can go and adjust the desired by hand in the console but that defeats the purpose of using terraform.

@bryantbiggs
Copy link
Member

we cannot parameterize the lifecycle/ignore_changes block so unfortunately we have taken the direction to ignore desired size changes since this is how the vast majority of users utilize the module

@llacoste
Copy link

Perhaps there could be a different node group type? eks_managed_no_autoscaling_node_groups or something similar?

@bryantbiggs
Copy link
Member

not in this module, no - we are doing everything we can currently to avoid any additional complexity overhead. the next breaking change at v19.x will actually remove the custom ASGs and launch templates so we can offload that to our https://github.com/terraform-aws-modules/terraform-aws-autoscaling module

@llacoste
Copy link

Okay, I'll wait to see what those changes entail. Thanks for the feedback.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 13, 2022
@bryantbiggs
Copy link
Member

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

No branches or pull requests

3 participants