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.):

controller key, duplicate certificates, controller rekey

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.3", GitCommit:"4957b090e9a4f6a68b4a40375408fdc74a212260", GitTreeState:"clean", BuildDate:"2016-10-16T06:36:33Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.3", GitCommit:"4957b090e9a4f6a68b4a40375408fdc74a212260", GitTreeState:"clean", BuildDate:"2016-10-16T06:20:04Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: self-hosted VM

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

Kernel (e.g. uname -a): 4.4.0-45

Install tools: Manual installation

Others:

What happened:

I generated an independent cert+key for each of my two controllers. Pods (especially kube-dns) had a high failure rate in talking to the apiserver. This showed up as 401 status in the apiserver log, and "the server requested the client to provide authenticate" in the pod kubedns log.

What you expected to happen:

I expected it to work. :)

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

Generate a different certificate and key for each controller machine (apiserver, controller manager, scheduler).

Load kube-dns.

Anything else do we need to know:

In many places, standard practice is to issue an independent certificate for each server. If Kubernetes doesn't support that configuration, it should be documented.

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/.): No

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

Unable to use a TTY

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

BUG REPORT

Kubernetes version (use kubectl version):

root@kube-master:# kubectl version

Client Version: version.Info{Major:"1", Minor:"4+", GitVersion:"v1.4.7-beta.0.2+1ef121737093fd-dirty", GitCommit:"1ef121737093fdefada11034782d235a205f567f", GitTreeState:"dirty", BuildDate:"2016-11-25T03:02:28Z", GoVersion:"go1.7.3 ibm-1.7", Compiler:"gc", Platform:"linux/ppc64le"}

Server Version: version.Info{Major:"1", Minor:"4+", GitVersion:"v1.4.7-beta.0.2+1ef121737093fd-dirty", GitCommit:"1ef121737093fdefada11034782d235a205f567f", GitTreeState:"dirty", BuildDate:"2016-11-25T03:02:28Z", GoVersion:"go1.7.3 ibm-1.7", Compiler:"gc", Platform:"linux/ppc64le"}

root@kube-master:#

Environment:

Cloud provider or hardware configuration: hardware configuration

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

NAME="Ubuntu"
VERSION="16.04.1 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.1 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
UBUNTU_CODENAME=xenial

Kernel (e.g. uname -a): Linux kube-master 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:38:24 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

Install tools:

Others:

What happened:

kubectl exec -it <pod_name> -- /bin/bash fails with error "Unable to use a TTY" and never get a prompt

root@kube-master:~# kubectl exec -it my-nginx-2833891535-ycsq2 -- /bin/bash
Unable to use a TTY - input is not a terminal or the right kind of file

=============> never get a prompt

What you expected to happen:

Could use kubectl exec -it <pod_name> -- /bin/bash to get the shell prompt of the POD.

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

Install Kubernetes 1.4.7

Deploy an application

Run kuectl exec -it <pod_name> -- /bin/bash

Anything else do we need to know:

I could use docker exec -it <container_name> /bin/bash to get the prompt, but kubectl exec does not work.