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

[Help] What is the right way to upgrade a nodegroup with different launch template version? #7786

Open
ok512 opened this issue May 29, 2024 · 7 comments
Labels
area/managed-nodegroup EKS Managed Nodegroups area/upgrades kind/help Request for help

Comments

@ok512
Copy link

ok512 commented May 29, 2024

eksctl version: 0.179.0

I'm trying to follow doc
Note:
If you're upgrading a node group that's deployed with a launch template to a new launch template version, add --launch-template-version version-number to the preceding command.

All these commands:

eksctl upgrade nodegroup --kubernetes-version 1.30 --profile tnet-dev --cluster test --name ng1
eksctl upgrade nodegroup --kubernetes-version 1.30 --profile tnet-dev --cluster test --name ng1 --launch-template-version 4
eksctl upgrade nodegroup --launch-template-version 4 --kubernetes-version 1.30 --profile tnet-dev --cluster test --name ng1

show error:
[ℹ] waiting for CloudFormation stack "eksctl-test-nodegroup-ng1"
Error: error fetching launch template data: operation error EC2: DescribeLaunchTemplateVersions,
https response error StatusCode: 400, RequestID: 98c3e445-3160-45e7-8c28-a469a875c5d2,
api error InvalidLaunchTemplateId.VersionNotFound:
Could not find the specified version 1 for the launch template with ID lt-0f3e2efa769a315f6.

Why and what for eksctl wants version 1 of launch template?
The nodegroup uses version 4 and it's default and latest launch template version too.

Am I missing something? 😕

@ok512 ok512 added the kind/help Request for help label May 29, 2024
Copy link
Contributor

Hello ok512 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl on our website

@cPu1
Copy link
Collaborator

cPu1 commented May 30, 2024

@ok512, did you happen to delete the version of the launch template the nodegroup was originally created with? Can you post the output of the following command, redacting any sensitive information?

$ aws ec2 describe-launch-template-versions --launch-template-id lt-0f3e2efa769a315f6

@cPu1 cPu1 added area/upgrades area/managed-nodegroup EKS Managed Nodegroups labels May 30, 2024
@ok512
Copy link
Author

ok512 commented May 31, 2024

did you happen to delete the version of the launch template the nodegroup was originally created with? Can you post the output of the following command, redacting any sensitive information?

Yes, because it's not used anywhere.
Why would it be a problem for eksctl?

Copy link
Contributor

github-actions bot commented Jul 1, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Jul 1, 2024
Copy link
Contributor

github-actions bot commented Jul 7, 2024

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 7, 2024
@cPu1 cPu1 removed the stale label Jul 22, 2024
@cPu1 cPu1 reopened this Jul 22, 2024
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Aug 22, 2024
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 27, 2024
@TiberiuGC TiberiuGC reopened this Sep 4, 2024
@github-actions github-actions bot removed the stale label Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/managed-nodegroup EKS Managed Nodegroups area/upgrades kind/help Request for help
Projects
None yet
Development

No branches or pull requests

3 participants