pulumi-eks: eks cluster creation fails with `Unhandled exception: TypeError: Cannot read properties of undefined (reading 'data')`

Hello!

  • Vote on this issue by adding a 👍 reaction
  • To contribute a fix for this issue, leave a comment (and link to your pull request, if you’ve opened one already)

Issue details

We use Amazon EKS pulumi component (using typescript) to create EKS clusters. the configuration looks more or less as follows -

const cluster = new eks.Cluster(`eks-cluster`, {
        // vpcId,
        endpointPrivateAccess: true,
        endpointPublicAccess: true,
        subnetIds: // subnet ids,
        nodeGroupOptions: {
            // nodetype, desired capacity etc
            nodeAssociatePublicIpAddress: false,
        },
        providerCredentialOpts: {
            roleArn,
        },
        nodeAssociatePublicIpAddress: false,
        createOidcProvider: true
    }, { provider: awsProvider });

the resources plugin versions

  • aws - 4.38.1
  • eks - 0.37.1

We have this setup for a few months now and recently started seeing this error.

Error - Unhandled exception: TypeError: Cannot read properties of undefined (reading 'data')

I am assuming this is being raised from one of these blocks - https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/cluster.ts#L563 (we do see log Cluster is ready which could be from here - https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/cluster.ts#L544)

I wonder if there is a version mismatch or any new parameters which need to be set on Cluster definition.

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 12
  • Comments: 21 (8 by maintainers)

Commits related to this issue

Most upvoted comments

Are there any workarounds or known working versions? Have since tried to revert back to previous packages but it no longer works and is always stuck with the same error.

I tried to add as much info as I can to help solve this

Also, to note, the PR #903 will likely resolve the immediate error being thrown, however, it will likely result in a kubeconfig which is incomplete due to not having the required clusters.cluster.certificate-authority-data property set.

Therefore I’m leaving this issue open to continue to investigate the root cause of the missing property.