kubeadm launches apiserver with bad flag

[pipejakob]

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

Versions

kubeadm version (use kubeadm version):
kubeadm version: version.Info{Major:"", Minor:"", GitVersion:"v0.0.0-master+$Format:%h$", GitCommit:"$Format:%H$", GitTreeState:"not a git tree", BuildDate:"1970-01-01T00:00:00Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}

(The reason the version/date are empty is because this was using the bazel-built .debs as part of the CI e2e jobs)

Environment:

• Kubernetes version (use kubectl version):
  Client Version: version.Info{Major:"", Minor:"", GitVersion:"v0.0.0-master+$Format:%h$", GitCommit:"$Format:%H$", GitTreeState:"not a git tree", BuildDate:"1970-01-01T00:00:00Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
• Cloud provider or hardware configuration:
  GCE
• OS (e.g. from /etc/os-release):
  NAME="Ubuntu"
  VERSION="16.04 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04 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 e2e-kubeadm-849-master 4.4.0-21-generic discuss the meaning of kubeadm init --api-advertise-addresses #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
• Others:

What happened?

When kubeadm init creates the apiserver manifest, it adds the flag --proxy-client-cert-file. This makes the apiserver exit immediately, printing its CLI usage info after this error message:

unknown flag: --proxy-client-cert-file

What you expected to happen?

I expected kubeadm init --kubernetes-version latest to bring up a functional control plane and exit successfully.

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

# Fetch/install the latest CI-built debs
$ mkdir /tmp/k8s-debs
$ gsutil rsync gs://kubernetes-release-dev/bazel/v1.7.0-alpha.0.1994+6f3e5bade60316/build/debs/ /tmp/k8s-debs
$ sudo dpkg -i /tmp/k8s-debs/*.deb
$ sudo apt-get install -f -y

$ sudo kubeadm init --kubernetes-version latest

Anything else we need to know?

This is causing the master kubeadm e2es to time out, since the control plane never comes up:

https://k8s-testgrid.appspot.com/google-gce#gce-kubeadm
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-kubeadm-gce/845

[pipejakob]

@mikedanese has a fix for this in review:

kubernetes/kubernetes#44002