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

Hello! I'm having a strange problem with setting up an eks cluster. I've inherited an older pulumi codebase, which is used in part to manage an EKS cluster.

The cluster is at version 1.25. However, when pulumi is setting up the vpc cni, it complains about `error: no matches for kind "CustomResourceDefinition" in version "<http://apiextensions.k8s.io/v1beta1|apiextensions.k8s.io/v1beta1>"`. The issue is similar to <https://github.com/pulumi/pulumi-eks/issues/720>.

I attempted to fix this issue by upgrading to the latest `@pulumi/eks`, but the problem persists, and pulumi keeps trying to use `kubectl` to apply an older  `amazon-k8s-cni.yaml`  file.

Found the issue. There was some weird caching that caused yarn to continue picking up the old pulumi-eks which targets `<http://apiextensions.k8s.io/v1beta1|apiextensions.k8s.io/v1beta1>` .

The problem went away after I switched over to npm.