unknown resource type eks:index:VpcCni

[shashiranjan84]

What happened?

After updating to EKS 3.5 and updating default node group(after setting AMI id), we seeing this error at end of deployment.

 Error: unknown resource type urn:pulumi:main.bob-infra.staging::bob-infra::eks:index:Cluster$eks:index:VpcCni::us-east-1-staging-bob-vpc-cni: Error: unknown resource type urn:pulumi:main.bob-infra.staging::bob-infra::eks:index:Cluster$eks:index:VpcCni::us-east-1-staging-bob-vpc-cni

To give a context, we currently on Kubernetes version 1.29 and trying to upgrade to 1.31. EKS and Kubernetes plugin version are respectively 2.2.1 and 4.8.1, which we also planning to upgrade to latest. So 1st we updated the EKS and K8s plugins to latest and then tried to update the cluster inline with explicit AL2023 NodeAmiId.

Example

const EKS_VERSION = '1.29';
const ami = pulumi.interpolate`/aws/service/eks/optimized-ami/${EKS_VERSION}/amazon-linux-2023/x86_64/nvidia/recommended/image_id`.apply((name) =>
      aws.ssm.getParameter({ name,  }, { async: true, provider: ... }),
    ).apply((result) => result.value);

const cluster = new eks.Cluster(
      `${regionalNamespace}-cluster`,
      {
        name: `${regionalNamespace}`,
        version: EKS_VERSION,
        vpcId: ...,
        privateSubnetIds: ...
        publicSubnetIds: ...,
        enabledClusterLogTypes: ['api', 'audit', 'authenticator'],
        tags: projectTags,
        endpointPrivateAccess: true,
        endpointPublicAccess: true,
        nodeAssociatePublicIpAddress: false,
        providerCredentialOpts: {
          profileName: aws.config.profile,
        },
        roleMappings: [
          ...
        ],
        instanceType: 'g5.2xlarge',
        // gpu: true,
       nodeAmiId: ami,
        nodeRootVolumeSize: 200,
        ...,
      },
      { provider: ... },
    );

Output of pulumi about

CLI          
Version      3.142.0
Go Version   go1.23.3
Go Compiler  gc

Host     
OS       debian
Version  11.7
Arch     x86_64

Backend        
Name           fv-az1490-728
URL            s3://prod-pulumi-state-transcend-io
User           root
Organizations  
Token type     personal

Additional context

Also noticed all addon getting redeployed every time we deploy some changes.

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[shashiranjan84]

cc @flostadler

[flostadler]

Thanks for opening this @shashiranjan84!
EKS v2.2.1 was affected by a bug (#1087) that made it use the latest version of the provider for the VPC CNI resource. This was fixed in v2.7.2.
Can you try upgrading to a more up-to-date version of v2 (e.g. v2.8.1) before going to EKS v3?

[shashiranjan84]

Thanks for opening this @shashiranjan84! EKS v2.2.1 was affected by a bug (#1087) that made it use the latest version of the provider for the VPC CNI resource. This was fixed in v2.7.2. Can you try upgrading to a more up-to-date version of v2 (e.g. v2.8.1) before going to EKS v3?

That not possible we already updated to EKS 3.5.0

[flostadler]

You can try removing the offending resource from state:

pulumi state delete 'urn:pulumi:main.bob-infra.staging::bob-infra::eks:index:Cluster$eks:index:VpcCni::us-east-1-staging-bob-vpc-cni'

After that pulumi up should work. In the meantime I'm gonna try to reproduce this behavior and if necessary update our migration guide.