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
If you invoke any of the ManagedNodeGroup options that result in a custom launch template being created, disk size cannot be set, as AWS expects the disk size to be set on the launch template, not the original request.
Example
See relevant PR
Output of pulumi about
Latest
Additional context
No response
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 @JustASquid. I saw you already started working on a PR, thanks a lot for that!
Let me know if you have any questions or need help getting it over the finish line
This fixes the handling of disk size changes when a custom launch
template is created for the MNG.
It is based on the Community PR #1229 by @JustASquid, I just added some
test fixes on top.
Fixes#1228
---------
Co-authored-by: Daniel West <daniel.west.279@gmail.com>
What happened?
If you invoke any of the
ManagedNodeGroup
options that result in a custom launch template being created, disk size cannot be set, as AWS expects the disk size to be set on the launch template, not the original request.Example
See relevant PR
Output of
pulumi about
Latest
Additional context
No response
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: