fresh-notebook-40503
07/07/2022, 6:59 PMeks.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?pulumi up
hangs for a while on "waiting for pods to be ready", and then I get errors like Minimum number of live Pods was not attained
. Makes sense - there are no nodes associated with the cluster. The default node group is not being created, even though the EC2 instances were createdbillowy-army-68599
flat-laptop-90489
07/07/2022, 7:54 PMfresh-notebook-40503
07/07/2022, 8:45 PM