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

Our cluster is also 1.23; I know 1.24 removed this apiVersion and I wonder if the latest pulumi-kubernetes provider is not checking the version first?

edit: I checked my kubeconfig and it does indeed have ``<http://client.authentication.k8s.io/v1alpha|client.authentication.k8s.io/v1alpha>`

I'll update that and see if it fixes it

```Unable to connect to the server: getting credentials: exec plugin is configured to use API version <http://client.authentication.k8s.io/v1beta1|client.authentication.k8s.io/v1beta1>, plugin returned version <http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>```
hmm nope, so I think since is being funky

Oh wowsers! so anyone else hitting this^ my awscli was sorta old: 2.4.x, I updated to 2.8.8 and with `aws eks update-kubeconfig` it properly put the right supported apiVersion in now and the tool is not returning errors.

This was the version I was using:
```⟩ aws --version
aws-cli/2.4.29 Python/3.8.8 Darwin/21.6.0 exe/x86_64 prompt/off```
This is the version that works correctly now:
```⟩ aws --version
aws-cli/2.8.8 Python/3.9.11 Darwin/21.6.0 exe/x86_64 prompt/off```