Hi everyone, I'm new to using Pulumi, so I'm also very new to using

cue

and

yaml

in general. I'm trying to build out a simple kubernetes cluster using AWS provider while using the

cue

compiler option. I started from the basic example provided on the

pulumi-yaml

project. When attempting to bring up the resources, I wanted to connect to the cluster with my local

kubectl

install. I ran into an error

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>

. I looked at the detailed output from Pulumi, and it seems to be creating the

kubeconfig

file with ``client.authentication.k8s.io/v1beta1`` instead of

<http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>

. I installed different versions of

kubectl

and

kubectl 1.21

works so far for me where I can connect, but it doesn't list in resources, since Pulumi failed to finish the rest of the resources. I'm not sure if this is the correct place to ask for help.

Ah, glad you figured this out! I believe this is an issue we're tracking on the EKS provider as well

thank you! i tore the cluster down and kept bring it back up, and i kept seeing that

v1beta1

but it seems upgrading my aws cli managed to ignore or rewrote

v1beta1

to

v1alpha

when I was able to connect the cluster to my local machine. but good to know that it is being tracked.