This reminds me that I found it is really a suffer to tell our end user to setup their kubectl configuration. say the user needs to type:

$ kubectl config set-cluster --server=xxx
$ kubectl config set-credentials xx --username=xxx password=xxxx
$ kubectl config set-context xxx --cluster=xxx --user=xxx --namespace=xxxx
$ kubectl config use-context xxxx

I think that's a lots of commands that user needs to remember and type, if we could provide a much simply command for the new, it would be much help. Like this one:

$ kubectl init <name> <server>
username: xxxx
password: xxxx

We have in the past said that "kubectl login ..." would do that for you,
but we need to sort out what login means when we have an arbitrary number
of possible ways to log in. Some of that discussion has been moving along.

On Tue, May 10, 2016 at 10:44 AM, zhouhaibing089 notifications@github.com
wrote:

This reminds me that I found it is really a suffer to teach end user to
setup their kubectl configuration. say the users need to type:

$ kubectl config set-cluster --server=xxx
$ kubectl config set-credentials xx --username=xxx password=xxxx
$ kubectl config set-context xxx --cluster=xxx --user=xxx --namespace=xxxx
$ kubectl config use-context xxxx

I think that's a lots of commands that user needs to remember and type, if
we could provide a much simply command for the new, it would be much help.
Like this one:

$ kubectl init username: xxxxpassword: xxxx

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub
#25383 (comment)

When this is added it would be nice if the bash completion could use it to power completion for use-context.

e.g.

kubectl config use-context aws_

completes to

kubectl config use-context aws_kubernetes

I'd like to work on this, can someone assign it to me please? I'll have a PR up soon.

@asalkeld that's awesome. @janetkuo ptal.

Note: I haven't added the tab completion for use-context, that completions bash script looks like serious magic :-O

See also #20605

For the record, here's a way to list contexts in v1.3: kubectl config view -o jsonpath='{.contexts[*].name}'

There's a friendlier command available now which shows all the current contexts, which one you're in, names, clusters, authinfo, and namespaces

$ kubectl config get-contexts