Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

kubectl "does not allow access"

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Bug report

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.6", GitCommit:"e569a27d02001e343cb68086bc06d47804f62af6", GitTreeState:"clean", BuildDate:"2016-11-12T05:22:15Z", GoVersion:"go1.7.1", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.5", GitCommit:"5a0a696437ad35c133c0c8493f7e9d22b0f9b81b", GitTreeState:"clean", BuildDate:"2016-10-29T01:32:42Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration:

GCP GKE 1.4.5

OS (e.g. from /etc/os-release):

Not sure, using gci

Kernel (e.g. uname -a):

Not sure, using gci

Install tools:

GKE web UI

Others:

N/A

What happened:

In juggling multiple gcloud accounts with GKE clusters I accidentally used kubectl with the wrong application default credentials and it cached bad creds in ~/.kube/config

After pointing gcloud at the right application default credentials and re-running kubectl, it continued trying and failing to use the bad creds cached in ~/.kube/config; at this point I was stuck and confused for a few hours

To repair, I had to manually edit ~/.kube/config to remove users[].user.auth-provider.config, and then kubectl started working again (or else wait ~1h for the access token to expire and refresh itself)

What you expected to happen:

After pointing gcloud at the right application default credentials kubectl should just work, or at least provide an error msg to the user that can help them figure out that they need to revoke the bad access token and how to do it

How to reproduce it (as minimally and precisely as possible):

Good scenario: just works

# Avoid calling kubectl with wrong application default credentials
gcloud auth application-default login # -> Auth with user A
kubectl --context cluster-A version # Ok + caches good creds
gcloud auth application-default login # -> Auth with user B
kubectl --context cluster-B version # Ok + caches good creds

# Both now work
kubectl --context cluster-A version # Ok, using cached good creds
kubectl --context cluster-B version # Ok, using cached good creds

Bad scenario: user makes one mistake and gets stuck

# Use kubectl with wrong ADC
gcloud auth application-default login # -> Auth with user A
kubectl --context cluster-A version # Ok + caches good creds
kubectl --context cluster-B version # Oops + caches bad creds
gcloud auth application-default login # -> Auth with user B
kubectl --context cluster-B version # Fails, stuck on bad creds cached in ~/.kube/config
kubectl --context cluster-A version # Still works, using cached good creds

# User is now stuck and confused with no clear approach to resolve...

# Tada!
vim ~/.kube/config # Manually remove users[].user.auth-provider.config for cluster-B
kubectl --context cluster-B version # Ok + caches good creds

# Both now work
kubectl --context cluster-A version # Ok, using cached good creds
kubectl --context cluster-B version # Ok, using cached good creds

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

Bug?

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

exec format error

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Kubernetes version (use kubectl version):

Build from source K8s master and 1.5.0a

Environment:

Cloud provider or hardware configuration:

Raspberry Pi 3

OS (e.g. from /etc/os-release):

HypriotOS 1.0

Kernel (e.g. uname -a):

Linux k8smaster 4.4.15-hypriotos-v7+ #1 SMP PREEMPT Mon Jul 25 08:46:52 UTC 2016 armv7l GNU/Linux

Install tools:

Others:

What happened:

Status: Downloaded newer image for gcr.io/google_containers/kube-cross:v1.6.3-9

---> e4ded450d60b

Step 2 : RUN touch /kube-build-image

---> Running in 309c88797965

standard_init_linux.go:175: exec user process caused "exec format error"

The command '/bin/sh -c touch /kube-build-image' returned a non-zero code: 1

To retry manually, run:

docker build -t kube-build:build-cc7f4ab6d3-4-v1.6.3-9 --pull=false /home/pirate/kubernetes/_output/images/kube-build:build-cc7f4ab6d3-4-v1.6.3-9

Makefile:239: recipe for target 'release' failed

make: *** [release] Error 1

What you expected to happen:

make release to complete

How to reproduce it (as minimally and precisely as possible):

o Download Hypriot flash tool: flash https://downloads.hypriot.com/hypriotos-rpi-v1.0.0.img.zip

o Flash image on SD card: http://blog.hypriot.com/post/releasing-HypriotOS-1-0/

o Boot rpi 3 from SD card

o git clone https://github.com/kubernetes/kubernetes.git

o cd kubernetes && make release

Anything else do we need to know:

docker version

Client:

Version: 1.12.1

API version: 1.24

Go version: go1.6.3

Git commit: 23cf638

Built: Thu Aug 18 05:31:15 2016

OS/Arch: linux/arm

Server:

Version: 1.12.1

API version: 1.24

Go version: go1.6.3

Git commit: 23cf638

Built: Thu Aug 18 05:31:15 2016

OS/Arch: linux/arm