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

you need to construct the Provider yourself - let me get you an example

here is an example in Go that you will be able to use to help you <https://github.com/pulumi/examples/blob/master/aws-go-eks/main.go#L143>

notice you need to construct a kubernetes Provider and then set the kubeconfig as part of it to allow interaction with the kubernetes cluster

There's a hard dependency on `aws-iam-authenticator` , is that going to work without kubectl? <https://github.com/pulumi/examples/blob/master/aws-go-eks/main.go#L250>

<@U01TGFGS25S> you can use `aws eks get-token` instead

This is what I went for, posting here in case someone stumbles on it.

FWIW - <https://github.com/pulumi/pulumi-eks/issues/11|https://github.com/pulumi/pulumi-eks/issues/11> is tracking adding this feature to the EKS package. 

I might look into contributing it, sounds like a good first issue. That being said, my main concern is whether to go with iam-authenticator, or going the `aws eks get-token` route