https://pulumi.com logo
Title
g

gorgeous-minister-41131

11/04/2022, 4:36 PM
Hello! I'm seeing this error when trying to use only the render to Yaml provider. I am explicitly passing the provider into the resource, and I have disabled the default providers for
*
-
error: failed to initialize discovery client: exec plugin: invalid apiVersion "<http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>"
I anticipate this is related to the kubectl client. For reference I'm using
kubectl version --client=true
Client Version: <http://version.Info|version.Info>{Major:"1", Minor:"23", GitVersion:"v1.23.7", GitCommit:"42c05a547468804b2053ecf60a3bd15560362fc2", GitTreeState:"clean", BuildDate:"2022-05-24T12:30:55Z", GoVersion:"go1.17.10", Compiler:"gc", Platform:"darwin/arm64"
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
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