No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

howdy, using aws native provider I've realised that once my Nodegroup is running, it seems bound to the ami id that was available at the time of the creation, is there a way to always stick to the latest ami ?
I suppose a workaround would be to fetch the k8s version from ssm and pass it to the launch template, etc

i tried passing a `release_version` explicitly (but I don't know how to get that version programmatically?), that worked but did not really update the anything, rather replaced the the whole node group with a new one