This message was deleted.

sparse-intern-71089

11/04/2022, 4:36 PM

This message was deleted.

gorgeous-minister-41131

11/04/2022, 4:46 PM

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 ``client.authentication.k8s.io/v1alpha` I'll update that and see if it fixes it

gorgeous-minister-41131

11/04/2022, 4:49 PM

Copy code

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

gorgeous-minister-41131

11/04/2022, 4:55 PM

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.

gorgeous-minister-41131

11/04/2022, 4:56 PM

This was the version I was using:

Copy code

⟩ 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:

Copy code

⟩ aws --version
aws-cli/2.8.8 Python/3.9.11 Darwin/21.6.0 exe/x86_64 prompt/off

28 Views

Open in Slack

Previous Next

Pulumi Community

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.