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

A workaround - and in fact best practice guidance - is to specify the AMI you want to use explicity so that you don't pick up new AMI versions automatically.

That said - we should definitely not be selecting ARM versions by default.

I see we just opened <https://github.com/pulumi/pulumi-eks/issues/110> to track fixing this.

Ah - great thanks. I initially missed the nodeAmiId property. Great to see that issue was found / raised at the same time :slightly_smiling_face:

Unfortunately due to the cloudformation rollback, the stack state is out of whack and won't update(tries to delete a launch config that is still in use). I tried a `refresh`, but that didn't help. I guess the only way is to export/import the stack state and try fix it manually.

Ok - sorted by manually duplicating the in-use launch config and assigning the copy to the auto scale group, then pulumi could delete the old and move on.

See also <https://github.com/pulumi/pulumi-eks/issues/88>