No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Can you provide info about how the `kubeconfig` stack output is being created, and what's in the JSON file itself? There are a lot of reasons this could be failing.

Do you know how authentication worked before (IAM authenticator, static token, etc)?

Here I'm using pulumi-eks rather than aws/eks to create the EKS cluster.

:point_up_2:The json file with some information removed.

That does look sufficient to have authentication work.

What happens when you run `AWS_PROFILE="&lt;your profile name&gt;" aws eks get-token --cluster &lt;your cluster name&gt;`, replacing the two values from the values in your JSON file?

If that prints out a token of some kind, I'm not sure what's wrong with your setup!

it does print out a valid token with a valid expiration date timestamp:
"expirationTimestamp": "2021-09-24T21:23:54Z"...

The only other thing I could think of is an outdated `kubectl` that doesn't understand the format of that JSON file.

I have a 1.21.3 version which is pretty new. not only kubectl doesn't work. Pulumi provider is broken as well (used to work). Not sure what the issue. Will keep digging into it. Thanks Jesse, for your help!