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

Hi folks,

I believe deployments might be blocked due to AWS change as of 2024/10/01
<https://github.com/SummitRoute/aws_breaking_changes/issues/95>

Hey <https://github.com/chrisvander|@chrisvander>, sorry you're running into this!
We're addressing the deprecation of the Launch Configuration resource by AWS in the <https://github.com/pulumi/pulumi-eks/issues/1425|next major release (v3)>.
We're aiming to release it towards the end of the week, but you can already check out the beta version if you'd like to: <https://github.com/pulumi/pulumi-eks/releases/tag/v3.0.0-beta.1|v3.0.0-beta.1>.

Otherwise you can work around this by not creating the default node group of the cluster and instead create one explicitly like mentioned in this comment: <https://github.com/pulumi/pulumi-eks/issues/1419#issuecomment-2396230169>

In case you're trying out the beta, please let us know about any problems/issues you're facing with it!

I also see that you mentioned karpenter in your original question. We have a feature request for adding built in karpenter support: <https://github.com/pulumi/pulumi-eks/issues/1114>
That being said, you can deploy karpenter today but you'll need to configure it yourself.

As described in the issue setting     `skipDefaultNodeGroup: true`  did the trick!

Was really a pain to debug, (I actually could not figure out that magic and whre lauch config came from)