That's confusing. If you ^C, it shouldn't even have a chance to create the .kube/config, should it? Unless it recycles a previous token? That sounds like a bad idea?

I'd nuke (or at least temporarily move) your ~/.kube directory and see if you can reproduce.

I did a ton of cluster up/down cycles with the bearer token change and never saw this. I also haven't seen it fail on Jenkins for GCE or GKE since the change went in.

it isn't creating the .kube/config.
And I had previously tried what Robby suggested.

Okay, I had kube-up print the command it is using to try and reach the master.

• when run directly on the command line, it fails with 401 unauthorized.
• when I use the crypt function to compare the password value I'm passing with the hash in the htpasswd file, it matches.
• when I try to access the master using several of the tokens, it works.

So, the problem seems to be on the server's handling of basic auth.

Grr. I'm on a branch prior to #6618

A config file is not being created for me -- .kubeconfig is still there and different from the output of kubectl config view @jlowdermilk