Update Kubernetes from v1.6.2 to v1.6.4

[dghubble]

• Update bootkube example cluster to v1.6.4
• Update bootkube (terraform-based) cluster to v1.6.4
• Update bootkube Terraform module to v1.6.4
• Uses bootkube v0.4.4 https://github.com/kubernetes-incubator/bootkube/releases/tag/v0.4.4

cc @aaronlevy @diegs

[dghubble]

Note: This PR won't pass tests until bootkube publishes the v0.4.4 bootkube.tar.gz

Testing clusters myself, looks good.

Self-hosted Kubernetes

$ kubectl --kubeconfig=assets/auth/kubeconfig get nodes
NAME                STATUS    AGE       VERSION
node1.example.com   Ready     9m        v1.6.4+coreos.0
node2.example.com   Ready     9m        v1.6.4+coreos.0
node3.example.com   Ready     9m        v1.6.4+coreos.0

$ kubectl --kubeconfig=assets/auth/kubeconfig get pods --all-namespaces
NAMESPACE     NAME                                       READY     STATUS    RESTARTS   AGE
kube-system   kube-apiserver-3s476                       1/1       Running   2          10m
kube-system   kube-controller-manager-439902065-h5ngz    1/1       Running   0          10m
kube-system   kube-controller-manager-439902065-mrsx4    1/1       Running   1          10m
kube-system   kube-dns-2431531914-zp3d0                  3/3       Running   0          10m
kube-system   kube-etcd-network-checkpointer-jg9j3       1/1       Running   0          10m
kube-system   kube-flannel-4vbcr                         2/2       Running   0          10m
kube-system   kube-flannel-5shdd                         2/2       Running   1          10m
kube-system   kube-flannel-kcmzl                         2/2       Running   0          10m
kube-system   kube-proxy-2h9pk                           1/1       Running   0          10m
kube-system   kube-proxy-48qwj                           1/1       Running   0          10m
kube-system   kube-proxy-761mx                           1/1       Running   0          10m
kube-system   kube-scheduler-824717717-mtbrw             1/1       Running   0          10m
kube-system   kube-scheduler-824717717-z228m             1/1       Running   0          10m
kube-system   pod-checkpointer-6h8lk                     1/1       Running   0          10m
kube-system   pod-checkpointer-6h8lk-node1.example.com   1/1       Running   0          9m

Self-hosted Kubernetes (w self-hosted etcd)

Pod Status:          kube-apiserver        Running
May 20 00:23:39 node1.example.com bootkube-start[1251]: [  534.769814] bootkube[5]:         Pod Status:        pod-checkpointer        Running
May 20 00:23:39 node1.example.com bootkube-start[1251]: [  534.770987] bootkube[5]:         Pod Status:          kube-apiserver        Running
May 20 00:23:40 node1.example.com bootkube-start[1251]: [  534.776738] bootkube[5]:         Pod Status:          kube-scheduler        Running
May 20 00:23:40 node1.example.com bootkube-start[1251]: [  534.781945] bootkube[5]:         Pod Status: kube-controller-manager        Running
May 20 00:23:40 node1.example.com bootkube-start[1251]: [  534.785039] bootkube[5]:         Pod Status:           etcd-operator        Running
May 20 00:23:40 node1.example.com bootkube-start[1251]: [  534.880108] bootkube[5]: All self-hosted control plane components successfully started
May 20 00:23:40 node1.example.com bootkube-start[1251]: [  534.894038] bootkube[5]: Migrating to self-hosted etcd cluster...
May 20 00:23:45 node1.example.com bootkube-start[1251]: [  540.682516] bootkube[5]: I0520 00:23:45.619772       5 migrate.go:51] created etcd cluster TPR
May 20 00:23:51 node1.example.com bootkube-start[1251]: [  546.117573] bootkube[5]: I0520 00:23:51.054826       5 migrate.go:62] etcd-service IP is 10.3.0.15
May 20 00:23:51 node1.example.com bootkube-start[1251]: [  546.154920] bootkube[5]: I0520 00:23:51.092192       5 migrate.go:67] created etcd cluster for migration
May 20 00:24:01 node1.example.com bootkube-start[1251]: [  556.160925] bootkube[5]: I0520 00:24:01.096948       5 migrate.go:72] etcd cluster for migration is now running
May 20 00:24:06 node1.example.com bootkube-start[1251]: [  561.191404] bootkube[5]: I0520 00:24:06.128639       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:11 node1.example.com bootkube-start[1251]: [  566.172832] bootkube[5]: I0520 00:24:11.110079       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:16 node1.example.com bootkube-start[1251]: [  571.167030] bootkube[5]: I0520 00:24:16.104297       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:21 node1.example.com bootkube-start[1251]: [  576.168203] bootkube[5]: I0520 00:24:21.105466       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:26 node1.example.com bootkube-start[1251]: [  581.169050] bootkube[5]: I0520 00:24:26.106313       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:31 node1.example.com bootkube-start[1251]: [  586.168514] bootkube[5]: I0520 00:24:31.105769       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:36 node1.example.com bootkube-start[1251]: [  591.184856] bootkube[5]: I0520 00:24:36.117930       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:41 node1.example.com bootkube-start[1251]: [  596.168395] bootkube[5]: I0520 00:24:41.105640       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:46 node1.example.com bootkube-start[1251]: [  601.167802] bootkube[5]: I0520 00:24:46.105045       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:51 node1.example.com bootkube-start[1251]: [  606.170666] bootkube[5]: I0520 00:24:51.107869       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:24:56 node1.example.com bootkube-start[1251]: [  611.198466] bootkube[5]: I0520 00:24:56.129300       5 migrate.go:203] still waiting for boot-etcd to be deleted...
May 20 00:25:01 node1.example.com bootkube-start[1251]: [  616.175660] bootkube[5]: I0520 00:25:01.112713       5 migrate.go:77] removed boot-etcd from the etcd cluster
May 20 00:25:06 node1.example.com bootkube-start[1251]: [  621.391209] bootkube[5]: Tearing down temporary bootstrap control plane...

^ loops and retries removals

kubectl --kubeconfig=assets/auth/kubeconfig get pods --all-namespaces
NAMESPACE     NAME                                       READY     STATUS    RESTARTS   AGE
kube-system   etcd-operator-3783208090-btx65             1/1       Running   1          3m
kube-system   kube-apiserver-kflrx                       1/1       Running   4          3m
kube-system   kube-controller-manager-439902065-fxhjn    1/1       Running   0          3m
kube-system   kube-controller-manager-439902065-qzpf9    1/1       Running   1          3m
kube-system   kube-dns-2431531914-n4qjw                  3/3       Running   0          3m
kube-system   kube-etcd-0000                             1/1       Running   0          2m
kube-system   kube-etcd-network-checkpointer-rg44g       1/1       Running   0          3m
kube-system   kube-flannel-2hf38                         2/2       Running   0          3m
kube-system   kube-flannel-kf6hh                         2/2       Running   0          3m
kube-system   kube-flannel-x7cr0                         2/2       Running   0          3m
kube-system   kube-proxy-8zwr7                           1/1       Running   0          3m
kube-system   kube-proxy-fp2qb                           1/1       Running   0          3m
kube-system   kube-proxy-gzfvn                           1/1       Running   0          3m
kube-system   kube-scheduler-824717717-9bbxd             1/1       Running   0          3m
kube-system   kube-scheduler-824717717-pdjvr             1/1       Running   1          3m
kube-system   pod-checkpointer-gkbrz                     1/1       Running   0          3m
kube-system   pod-checkpointer-gkbrz-node1.example.com   1/1       Running   0          3m