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

Should I be manually re-applying the manifest for this? My cluster is currently down due to this problem

How did you create the CNI in the first place?

If you didn't specify a way to manage it, then EKS just creates it, but doesn't manage it or update it. (thanks EKS)

Looks like Pulumi provides a resource for this: <https://www.pulumi.com/registry/packages/eks/api-docs/vpccni/>

So I used `new eks.Cluster` to provision my eks nearly a year ago - and if eks creates this, wouldn’t it create problems to also create it via pulumi’s vpccni resource? What do you suggest? Should I just update it manually?

honestly not sure, I haven’t used the pulumi resource myself yet.

Updating manually is probably safe to get you un-stuck. You can always import later

OK that’s what I thought - thank you for your help!

Oh one more quick thing <@U02EZJWEF62> - should I also run `pulumi refresh` after updating manually to make sure my pulumi state is in sync with eks state?