https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
b
aws-iam-authenticator
is (I believe) deprecated. You can build a Pulumi provider from our EKS module pretty easily - which language SDK are you uisng?
b
my EKS cluster is managed by Terraform right now 😕 I'm using TS
b
are you trying to rebuild the components from terraform?
b
https://registry.terraform.io/modules/terraform-aws-modules/eks/aws/latest?tab=outputs The kubeconfig from that module uses aws-iam-authenticator, which is frankly annoying.
I'm not sure what you mean by rebuild the components
b
do you have an existing 
kubeconfig
you want to use?
b
No. I used the 
kubeconfig
output from that Terraform module but I don't even use that within Terraform (I used what I posted in the initial message) in the TF Kubernetes provider
I would actually even prefer to manage the EKS cluster using pulumi, but that would be quite a massive endeavour to import into Pulumi. It would probably be easier to delete the cluster from TF, and re-create it using Pulumi
b
i'm assuming here you want to use the existing cluster defined in terraform and then create a Pulumi provider to create Kubernetes resources, in which case, you have 2 options: run 
aws eks update-kubeconfig --name <your cluster name> --kubeconfig /tmp/kube
which will generate you a kubeconfig you can use pulumi-terraform to grab the outputs and build the provider manually like you do in terraform
b
you can use pulumi-terraform to grab the outputs and build the provider manually like you do in terraform
This is exactly what I would like to do
The K8S provider in Terraform accepts inputs such as 
token
, the Pulumi one does not, so I don't know if this is doable at this time
b
it doesn't, we don't build our Kubernetes provider from the terraform one, you'll need to generate a kubeconfig somehow
now I realise it, I don't think you can do option 2 without doing a bunch of manual querying...
b
I don't think the aws-iam-authenticator is deprecated: https://github.com/kubernetes-sigs/aws-iam-authenticator (but man, it should never has existed...)
b
if you run 
aws eks get-kubeconfig
it'll get you a valid kubernetes kubeconfig which you can pass to Pulumi, I would highly recommend that approach
b
Yeah that's what I'll do. I was hoping to reduce the number of external dependencies (since 
aws eks update-kubeconfig
requires 
kubectl
) Cheers 🙂
11 Views
Open in Slack
PreviousNext
Powered by

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.

Powered by