This message was deleted.

@stocky-petabyte-29883 the provider/generated kubeconfig that is created uses aws profiles if you're using profiles as the auth mechanism. you can see that by outputting the kubeconfig generated, it ends up looking a bit like this:

{
  "apiVersion": "v1",
  "clusters": [
    {
      "cluster": {
        "certificate-authority-data": "<redacted>",
        "server": "<redacted>"
      },
      "name": "kubernetes"
    }
  ],
  "contexts": [
    {
      "context": {
        "cluster": "kubernetes",
        "user": "aws"
      },
      "name": "aws"
    }
  ],
  "current-context": "aws",
  "kind": "Config",
  "users": [
    {
      "name": "aws",
      "user": {
        "exec": {
          "apiVersion": "<http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>",
          "args": [
            "eks",
            "get-token",
            "--cluster-name",
            "lbriggs-eks-example-eksCluster-a60dd34"
          ],
          "command": "aws",
          "env": [
            {
              "name": "AWS_PROFILE",
              "value": "pulumi-dev-sandbox"
            }
          ]
        }
      }
    }
  ]
}