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.

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

Feature/cli.auth.token.support #13

Merged
merged 10 commits into from
Mar 7, 2020
Merged

Conversation

aleksandrmelnikov
Copy link
Contributor

No description provided.

util/kubeconfig.go Outdated Show resolved Hide resolved
@rushtehrani
Copy link
Contributor

Looks like with GKE, we have to run a kubectl first, then get the token. A newly created cluster doesn't have the token. Not sure if this is something we can do in code or just document.

$ go run main.go auth token

$ kubectl get nodes
NAME                                         STATUS   ROLES    AGE     VERSION
<node-1-name>    Ready    <none>   3m51s   v1.15.8-gke.3
<node-2-name>    Ready    <none>   5m13s   v1.15.8-gke.3
<node-e-name>    Ready    <none>   5m13s   v1.15.8-gke.3
$ go run main.go auth token
<token-was-returned>

@rushtehrani rushtehrani merged commit 56d0bdd into master Mar 7, 2020
@rushtehrani rushtehrani deleted the feature/cli.auth.token.support branch March 7, 2020 23:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants