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

I was searching on internet and I see that it refers to kubectl binary version.

Can I use <https://github.com/Azure/setup-kubectl> to install the 1.23 version of kubectl ?.

Also, do you have any guide of how to install aws-cli in a github action runner ?

oh sorry yes, are you provisioning an EKS cluster?

Yes, I have an eks cluster created already.

yep, its the aws cli version: <https://github.com/pulumi/pulumi-eks/issues/600>

update it, I'm not sure how to do that in github actions, I'm sure there's a setup aws cli action

by default the ubuntu runner that im using brings these versions:

• AWS CLI 2.6.1
• AWS CLI Session manager plugin 1.2.312.0


Which version is the recommended to fix this ?

not entirely sure I'm afraid, which version of eks are you using?

I have a version by default more newer that the described in the url that you sent me.

```    "dependencies": {
        "@pulumi/aws": "^3.2.1",
        "@pulumi/awsx": "^0.22.0",
        "@pulumi/kubernetes": "^2.5.1",
        "@pulumi/pulumi": "^2.0.0"
    }```

To which one ?. Can you please give me the good version ?

<https://github.com/pulumi/pulumi-eks/releases/tag/v0.39.0>

Empty KUBERNETES_EXEC_INFO, defaulting to <http://client.authentication.k8s.io/v1alpha1|client.authentication.k8s.io/v1alpha1>. This is likely a bug in your Kubernetes client. Please update your Kubernetes client.

that appears to be a different error, can you share your code and GitHub action configuration?

Sure, I will share the code with you using PM.

Hi, im also having this issue, after upgrading to pulumi-eks-0.40.0 &amp; pulumi-aws/sdk/v5-v5.1.2.
(upgraded both at the same time)
using aws-cli/2.5.6

seems upgrading to `aws-cli/2.7.2` worked.
kindof difficult to figure that out from that error