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

We should ignore changes to node ASG desired_capacity #38

Closed
1 task
max-rocket-internet opened this issue Jun 26, 2018 · 2 comments
Closed
1 task

We should ignore changes to node ASG desired_capacity #38

max-rocket-internet opened this issue Jun 26, 2018 · 2 comments

Comments

@max-rocket-internet
Copy link
Contributor

I have issues

I'm submitting a

  • feature request

The reason is that after cluster creation, almost everyone will run the k8s node autoscaler. This autoscaler is changing the desired_capacity to suit resources required by the cluster. So when the cluster autoscales, then TF is run again later, you see something like this:

  ~ module.cluster_1.aws_autoscaling_group.workers
      desired_capacity:   "5" => "3"

You can just add a lifecycle statement to resource aws_autoscaling_group.workers:

  lifecycle {
    ignore_changes = [ "desired_capacity" ]
  }
@brandonjbjelland
Copy link
Contributor

Heh you're on the same wavelength as @ozbillwang . He submitted this exact change 16 hours ago here: https://github.com/terraform-aws-modules/terraform-aws-eks/pull/36/files

I'll close this now and plan to release over the next day or so. Closing this up.

@github-actions
Copy link

github-actions bot commented Dec 5, 2022

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 Dec 5, 2022
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

2 participants