Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When getting an existing cluster, there isn't a way to pull the kubeconfig #97

Closed
metral opened this issue Feb 22, 2019 · 4 comments
Closed

When getting an existing cluster, there isn't a way to pull the kubeconfig #97

metral opened this issue Feb 22, 2019 · 4 comments
Labels
kind/enhancement Improvements or new features resolution/duplicate This issue is a duplicate of another issue

Comments

@metral
Copy link

metral commented Feb 22, 2019

In the current cluster object, we can use the cluster props: certificateAuthority, name, and endpoint to fill in the blanks in the kubeconfig file https://gist.github.com/b01eeecacccc3e284771463ed626af5e

we only do this right now in the object constructor, when we should actually have a kubeconfig() method on the object.

see community slack: https://pulumi-community.slack.com/archives/C84L4E3N1/p1550871454193500?thread_ts=1550862777.160400&cid=C84L4E3N1

related: pulumi/pulumi-aws#478
@metral metral self-assigned this Feb 22, 2019
@NinoFloris
Copy link

Is there some workaround besides manually templating the kubeconfig?

@lukehoban
Copy link
Member

For now - you need to copy the boilerplate from one of the examples - like https://github.com/pulumi/examples/blob/master/gcp-ts-gke/cluster.ts#L27.

This issue is tracking putting that boilerplate behind a named function in the @pulumi/gcp package, but should not technically be a blocker for any scenarios.

@NinoFloris
Copy link

Thanks so much for the fast response!

@stack72 stack72 mentioned this issue Dec 22, 2019
Closed
@mikhailshilkov mikhailshilkov added the kind/enhancement Improvements or new features label Jan 30, 2023
@jkodroff jkodroff mentioned this issue Apr 19, 2023
Open
@mikhailshilkov mikhailshilkov added the resolution/duplicate This issue is a duplicate of another issue label Jul 28, 2023
@mikhailshilkov
Copy link
Member

Closing as a dupe of #1064

@mikhailshilkov mikhailshilkov closed this as not planned Won't fix, can't repro, duplicate, stale Jul 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement Improvements or new features resolution/duplicate This issue is a duplicate of another issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lukehoban @metral @mikhailshilkov @NinoFloris