I got the error:

Type                                   Name                                  Status                  Info
 +   pulumi:pulumi:Stack                    aws-eks-crosswalk-dev                 **creating failed**     1 error; 1 mes
 +   └─ eks:index:Cluster                   cluster                               created                 
 +      ├─ eks:index:ServiceRole            cluster-instanceRole                  created (5s)            
 +      │  ├─ aws:iam:Role                  cluster-instanceRole-role             created (1s)            
 +      │  ├─ aws:iam:RolePolicyAttachment  cluster-instanceRole-3eb088f2         created (0.78s)         
 +      │  ├─ aws:iam:RolePolicyAttachment  cluster-instanceRole-03516f97         created (1s)            
 +      │  └─ aws:iam:RolePolicyAttachment  cluster-instanceRole-e1b295bd         created (1s)            
 +      ├─ eks:index:ServiceRole            cluster-eksRole                       created (5s)            
 +      │  ├─ aws:iam:Role                  cluster-eksRole-role                  created (1s)            
 +      │  └─ aws:iam:RolePolicyAttachment  cluster-eksRole-4b490823              created (1s)            
 +      ├─ eks:index:RandomSuffix           cluster-cfnStackName                  created (0.38s)         
 +      ├─ aws:ec2:SecurityGroup            cluster-eksClusterSecurityGroup       created (3s)            
 +      ├─ aws:iam:InstanceProfile          cluster-instanceProfile               created (1s)            
 +      ├─ aws:ec2:SecurityGroupRule        cluster-eksClusterInternetEgressRule  created (1s)            
 +      ├─ aws:eks:Cluster                  cluster-eksCluster                    created (390s)          
 +      ├─ aws:ec2:SecurityGroup            cluster-nodeSecurityGroup             created (3s)            
 +      ├─ pulumi:providers:kubernetes      cluster-eks-k8s                       created (0.18s)         
 +      ├─ eks:index:VpcCni                 cluster-vpc-cni                       **creating failed**     1 error
 +      └─ kubernetes:core/v1:ConfigMap     cluster-nodeAccess                    **creating failed**     1 error

Diagnostics:
  kubernetes:core/v1:ConfigMap (cluster-nodeAccess):
    error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "<https://88AAB92130837B759AFE4263F0FCBA4A.gr7.eu-west-1.eks.amazonaws.com/openapi/v2?timeout=32s>": getting credentials: decoding stdout: couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:\"apiVersion,omitempty\""; Kind string "json:\"kind,omitempty\"" }

  eks:index:VpcCni (cluster-vpc-cni):
    error: Command failed: kubectl apply -f /tmp/tmp-23051B6NEx6zsek0N.tmp
    Unable to connect to the server: getting credentials: decoding stdout: couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:\"apiVersion,omitempty\""; Kind string "json:\"kind,omitempty\"" }

  pulumi:pulumi:Stack (aws-eks-crosswalk-dev):
    Unable to connect to the server: getting credentials: decoding stdout: couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:\"apiVersion,omitempty\""; Kind string "json:\"kind,omitempty\"" }

    error: update failed

Resources:
    + 17 created

Duration: 6m47s

In case of creating clusters it is usually a 'big thing". Imean that creting such resource takes time. I encountered situations, where cluster took longer to create in cloud, but pulumi already went further. So in your case, I assume that pulumi assumed cluster is launched, while in fact in AWs it was still setup So you can first confir this is the case, and check AWS status directly from console, or aws command maybe. Aditionally I advise to use "depends" when creating resources https://www.pulumi.com/docs/concepts/options/dependson/

its great when it works 🙂