Having an issue with

eks.Cluster

. The EC2 instances are being created, but they are not being associated with the EKS cluster. Specifically, the default node group is not being created. Also, the OIDC provider is created, but it is not associated with the EKS cluster. Everything was working earlier, but then I created a new AWS account and started using AWS profiles to stand up infrastructure in the new account. All other components are being created properly in the new AWS account

const eksCluster = new eks.Cluster("eks-cluster", {
    vpcId: vpc.id,
    publicSubnetIds: vpc.publicSubnetIds,
    privateSubnetIds: vpc.privateSubnetIds,
    nodeAssociatePublicIpAddress: false,
    instanceType: "m5.large",
    desiredCapacity: 2,
    minSize: 2,
    maxSize: 4,
    createOidcProvider: true,
    roleMappings: [
      {
        groups: ["system:masters"],
        roleArn: clusterAdminRole.arn,
        username: "pulumi:admin-user",
      }
    ],
    providerCredentialOpts: {
      profileName: aws.config.profile,
    }
  });

Has anyone run into this problem before?

do the nodes get created in the same AWS account?

I've had many different reasons that node groups don't end up getting attached to clusters. Outside of missing IAM roles, networking is a big one. Usually though, I have to ssh to the node and go digging through boostrap script logs, kubelet logs, etc.

the nodes are successfully being created in the same AWS account, but they are not being associated with the eks cluster. good call! I'll ssh into the created nodes and look through the logs there. thanks!