Login should be enough to get kubeconfig

upbound / up

The @upbound CLI

Apache License 2.0

52 stars 41 forks source link

Login should be enough to get kubeconfig #338

Closed sttts closed 2 months ago

sttts commented 1 year ago

What problem are you facing?

$ up login
$ up cfg list
NAME                    ID                                     STATUS   DEPLOYED CONFIGURATION     CONFIGURATION STATUS
sttts-test              b5634552-731b-430f-bd9c-0753a0ec557a   ready    up-test-configuration      ready
$ up ctp kubeconfig get -a upbound sttts-test
up: error: missing flags: --token=STRING

This is unexpected that one needs a service account (API token).

How could Upbound help solve your problem?

Epic #

AlainRoy commented 1 year ago

Just for reference, it is documented: https://docs.upbound.io/cli/command-reference/#controlplane-kubeconfig-get https://docs.upbound.io/concepts/managed-control-planes/#connect-directly-to-your-mcp

Stefan, do you have a proposal for an alternate approach? Do you think the token should be auto-generated? Another authentication method should be used?

sttts commented 10 months ago

--generate-token that calls the API to create a token.

haarchri commented 2 months ago

all possible now with up ctx