AWS EKS nodegroup creation not working when only metadata version 2 is allowed: could not get token
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
Undecided
|
Thomas Bechtold |
Bug Description
Using the latest Ubuntu 1.19 image (ami-0ee92b4288
Steps to reproduce:
1) follow https:/
2) follow https:/
3) while setting up the launch template in 2), select
- Metadata accessible: Enabled
- Metadata version: v2 (token required)
- Metadata hop limit: 1
The nodegroup creation will fail with that. The reason is the client authentication method we use:
# /usr/bin/
could not get token: NoCredentialPro
You can verify that this is the reason with:
$ aws ec2 modify-
and then in the instance, "heptio-
Changed in cloud-images: | |
status: | New → In Progress |
assignee: | nobody → Thomas Bechtold (toabctl) |
summary: |
- AWS EKS nodegroup not working when only metadata verions 2 is allowed + AWS EKS nodegroup not working when only metadata version 2 is allowed |
summary: |
- AWS EKS nodegroup not working when only metadata version 2 is allowed + AWS EKS nodegroup not working when only metadata version 2 is allowed: + could not get token |
summary: |
- AWS EKS nodegroup not working when only metadata version 2 is allowed: - could not get token + AWS EKS nodegroup creation not working when only metadata version 2 is + allowed: could not get token |
Changed in cloud-images: | |
status: | In Progress → Fix Released |