hi all! I have some existing clusters and trying to upgrade EKS and addon versions. I'm trying to switch to pulumi-eks 3+ for that but am running into problems (previously used pulumi-eks 2.2) the current cluster doesn't have vpc-cni addon because we're using cilium instead. however when i run pulumi up it keeps getting created. I looked through the new parameters for eks.Cluster like VpcCniOptionsArgs but can't find a way to turn it off. I also can't figure out if there's a implicit dependency or something that would prompt pulumi to add it? I can't use default_addons_to_remove because the cluster already exists. is there a way to explicitly prevent pulumi from attaching the addon? or a way to find out what the implicit dependencies are?

You should be able to do that by setting the

useDefaultVpcCni

property to true. Admittedly, that name is not the most intuitive, but it essentially means: "don't bother managing the VPC CNI and just use whatever version of VPC CNI AWS created the cluster with (i.e. the default)". as for updating, I'd recommend you to first go to the latest version of the v2 major release before jumping to v3. There's been a couple of bug fixes between 2.2 and the newest v2 version and that would offer a more stable starting point

I see! I wouldn't have thought of that but makes sense, let me give it a go. appreciate the help!