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

Did you set `creationRoleProvider` when you created the cluster? I ran into this issue when I first set up EKS and my solution was to use this parameter with a shared admin role. If you don't do this, the cluster is created with whatever your current AWS credentials are.

if i already created the cluster without it what can i do now?

we had another cluster we had this problem with but using the rolemapping auth works fine

I might've fixed this by editing my state file directly, but you also might be able to fix by just setting `creationRoleProvider` and updating the program.