I’m trying to follow the EKS tutorial <https://www...
# kubernetes
I’m trying to follow the EKS tutorial https://www.pulumi.com/docs/guides/crosswalk/aws/eks/ and running into this error right out of they gate when I try to provision the cluster. Isn’t it supposed to install into the default VPC? What am I missing?
Copy code
(venv) a  devops git:(master) ✗ pulumi up
Previewing update (dev):
     Type                                   Name                                Plan       Info
     pulumi:pulumi:Stack                    devops-dev                        4 errors
 +   └─ eks:index:Cluster                   test-cluster                        create
 +      ├─ eks:index:ServiceRole            test-cluster-eksRole                create
 +      │  ├─ aws:iam:Role                  test-cluster-eksRole-role           create
 +      │  ├─ aws:iam:RolePolicyAttachment  test-cluster-eksRole-90eb1c99       create
 +      │  └─ aws:iam:RolePolicyAttachment  test-cluster-eksRole-4b490823       create
 +      ├─ eks:index:ServiceRole            test-cluster-instanceRole           create
 +      │  ├─ aws:iam:Role                  test-cluster-instanceRole-role      create
 +      │  ├─ aws:iam:RolePolicyAttachment  test-cluster-instanceRole-03516f97  create
 +      │  ├─ aws:iam:RolePolicyAttachment  test-cluster-instanceRole-e1b295bd  create
 +      │  └─ aws:iam:RolePolicyAttachment  test-cluster-instanceRole-3eb088f2  create
 +      ├─ eks:index:RandomSuffix           test-cluster-cfnStackName           create
 +      └─ aws:iam:InstanceProfile          test-cluster-instanceProfile        create

  pulumi:pulumi:Stack (devops-dev):
    error: Error: invocation of aws:ec2/getVpc:getVpc returned an error: invoking aws:ec2/getVpc:getVpc: 1 error occurred:
        * no matching VPC found
# ...... Long stacktace continues
yes it should, do you have a default VPC in the region you're installing it? some accounts delete it
Yes, I have a default VPC in the region. It does have the old style shorter VPC ID if that makes a difference.
does it have subnets in it? this is where we detect the VPC. https://github.com/pulumi/pulumi-eks/blob/c0d357bdf3f283006f8b0a6cd4bc2f1c09df34c0/nodejs/eks/cluster.ts#L399-L404
Copy code
export const vpc = aws.ec2.getVpc({ default: true }
Should return something
I ended up explicitly creating a VPC and subnets.