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

Change instance type for nextgen-dev nodes #12

Open
jonmjoyce opened this issue Sep 25, 2023 · 1 comment
Open

Change instance type for nextgen-dev nodes #12

jonmjoyce opened this issue Sep 25, 2023 · 1 comment

Comments

@jonmjoyce
Copy link
Member

I have another task when you get time, not urgent but just trying to reduce our EC2 costs. Could you change out the node group for the nextgen-dev cluster to m6i.large instance type, running 2 of them? Currently we are using 2 m5.xlarge but we don't need that many resources right now. Usually I create a new node group. Then to get the tags properly applied to the instances you edit the autoscaling group that gets created to add all of our required custom tags. Then if that all goes well you should be able to remove the old node group and the pods/resources should transfer over. There might be another way to do it but that's been my method. Thanks!

@pavaniankam92
Copy link
Collaborator

It is a good approach of creating a new group but there a few extra steps when compared with the other way.

The other way I wanted to share is that

  • First launch a new template with a new version (existing version is 6)
  • Update auto scaling group to point to the latest launch template
  • Capture any of the additional , EBS volumes are attached to the existing instance
  • Terminate the existing instance so that the ASG will create new instances with the latest launch template

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

No branches or pull requests

2 participants