https://pulumi.com logo
Title
p

proud-pizza-80589

01/31/2023, 5:51 PM
Is it me or is the eks cluster creation broken? My code that has been working for 2 years no longer does for making a new one, and i redid it coming from the recent template and i’m getting the same error. Totally unsure where the CRD’s are supposed to come from. There is a cni addon, but i need the cluster first before i can install it right? Code is simple as in the example:
// Create a new VPC
    const eksVpc = new Vpc('eks-vpc', {
      enableDnsHostnames: true,
      cidrBlock: '10.0.0.0/16',
    });

    // Create the EKS cluster
    this.cluster = new Cluster(name, {
      // Put the cluster in the new VPC created earlier
      vpcId: eksVpc.vpcId,
      // Public subnets will be used for load balancers
      publicSubnetIds: eksVpc.publicSubnetIds,
      // Private subnets will be used for cluster nodes
      privateSubnetIds: eksVpc.privateSubnetIds,
      // Change configuration values to change any of the following settings
      instanceType: 't3.large',
      desiredCapacity: 3,
      minSize: 3,
      maxSize: name.endsWith('-staging') ? 5 : 50,
      // Do not give the worker nodes public IP addresses
      nodeAssociatePublicIpAddress: false,
    });
n

narrow-finland-76022

01/31/2023, 5:57 PM
Looks like you aren't specifying a k8s version so it defaults to the latest. In this case looks like latest version doesn't support beta api you were leveraging.
p

proud-pizza-80589

01/31/2023, 5:58 PM
yeah, it deploys a .23, my existing ones are .21. But this means the “defaults” of the eks package are broken
n

narrow-finland-76022

01/31/2023, 5:59 PM
Are you using the latest version of the aws pulumi package?
p

proud-pizza-80589

01/31/2023, 5:59 PM
yes
"@pulumi/aws": "5.28.0",
    "@pulumi/awsx": "1.0.1",
    "@pulumi/eks": "1.0.1",
n

narrow-finland-76022

01/31/2023, 6:01 PM
Not with Pulumi myself , but need to make a cluster later today so I'll comment back if I run into the same issue
p

proud-pizza-80589

01/31/2023, 7:00 PM
same issue with cluster version 1.22
adding useDefaultVpcCni: true, makes it work
n

narrow-finland-76022

01/31/2023, 8:35 PM
Thanks, good to know