This message was deleted.

I worked a PR for the karpenter role that actually ended up just exposing a deeper issue in the full pulumi code that comes from the cross-language generation portion. I imagine you could fairly easily resolve your current issue with the same style PR, and end up exposing the same underlying issue which I can't remember... but the last time I checked it was still open.

Hi @clever-dog-35937 and thanks for your reply. My intent is exactly that, install karpenter after the EKS cluster creation. Any suggestions on how to do that..?....thanks...

Took me awhile to get back around to digging it up, but after that PR was merged in it exposed this issue which is still open: https://github.com/pulumi/pulumi/issues/11726. I haven't taken the time to go back through and open another example issue with it, because all it would be doing it pointing back to the already open issue 😕 Watching that one for when it closes, one of my primary gripes with pulumi right now is that the teams will release something awesome in a blog post and then it becomes basically abandoned without getting past the POC stage into even some sort of expandable MVP. A la their eks blueprints and ssp https://www.pulumi.com/blog/eks-blueprints-for-pulumi/