You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLI
Version 3.142.0
Go Version go1.23.3
Go Compiler gc
Host
OS debian
Version 11.7
Arch x86_64
Backend
Name fv-az1490-728
URL s3://staging-pulumi-state-io
User root
Organizations
Token type personal
Additional context
Even when I tried to hardcode amiID in managed node group, it was ignored.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
Sorry you're running into this @shashiranjan84. This is indeed a bug in pulumi-eks.
Right now the custom AMI gets only set if custom userdata is needed for the underlying Launch Template. A custom AMI is also a reason for including custom userdata, but that's missing right now.
What happened?
When I create a managed node group with a amiID, worker node instance do not have same amiID.
Example
Output of
pulumi about
CLI
Version 3.142.0
Go Version go1.23.3
Go Compiler gc
Host
OS debian
Version 11.7
Arch x86_64
Backend
Name fv-az1490-728
URL s3://staging-pulumi-state-io
User root
Organizations
Token type personal
Additional context
Even when I tried to hardcode amiID in managed node group, it was ignored.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: