https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
c
@busy-umbrella-36067 hmm not sure what you mean.. can’t you do something like:
Copy code
// Create an EKS cluster with the default configuration.
const cluster = new eks.Cluster("cluster");

// Export the cluster's kubeconfig.
export const kubeconfig = cluster.kubeconfig;
g
I think what @busy-umbrella-36067 means is something similar to this https://gist.github.com/geekflyer/b78adab2667d8526a1dd593bc5c844bf#file-gke-ts-L33-L66 to be made part of the eks package. I actually thought along the same lines for the gcp package.
b
@creamy-potato-29402 the eks cluster is created outside of pulumi
@glamorous-printer-66548 yup. I think AWS has an API call that will output the config for you, so you wouldn't even have to do much
g
@busy-umbrella-36067 i don’t see getting the kubectl config from either terraform or AWS’s API directly (checked the docs). Where do you get that info from? That being said i think pulumi could add it anyways.
b
I guess it might be awscli only
g
yep looks like, this is similar to 
gcloud container clusters get-credentials
which generates a kubectl config but is also only part of the CLI
b
So pretty much exactly your gist @glamorous-printer-66548
For AWS
c
@busy-umbrella-36067 ah. Got it. Can you file it against EKS repo itself?
✔️ 1
b
I like this idea. In fact, it would be nice to try to achieve this for all flavors of hosted clusters. We had to do something dubious and questionable for GKE: https://github.com/pulumi/examples/blob/0cd79d7c10bd5198f13326d2660d84fbd60fa5ed/gcp-ts-gke/cluster.ts#L27
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