Code change:
params+=" --advertise-address=${vm_external_ip}" params+=" --ssh-user=${PROXY_SSH_USER}" params+=" --ssh-keyfile=/etc/srv/sshproxy/.sshkeyfile" <del> else [ -n "${MASTER_ADVERTISE_ADDRESS:-}" ] </del> <ins> elif [ -n "${MASTER_ADVERTISE_ADDRESS:-}" ]; then </ins> params="${params} --advertise-address=${MASTER_ADVERTISE_ADDRESS}" fi

Related discussion:
text: NAME ZONE MACHINETYPE PREEMPTIBLE INTERNALIP EXTERNAL_IP STATUS kubernetes-master us-central1-b n1-standard-1 10.128.0.2 23.236.62.71 RUNNING == Waiting for new master to respond to API requests == ..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
I'm seeing this problem as well. And I saw this on two of the hosts: [ 3870.] Memory cgroup out of memory: Kill process 4697 (google-fluentd) score 1923 or sacrifice child [ 3870.] Killed process 4697 (google-fluentd) total-vm:1224416kB, anon-rss:186420kB, file-rss:8068kB
cc:
After syncing up with This is what we saw in the master configuration. rkouj /var/log $ sudo systemctl status kube-master-configuration kube-master-configuration.service - Configure kubernetes master Loaded: loaded (/etc/systemd/system/kube-master-configuration.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2016-11-22 21:06:55 UTC; 1h 24min ago Process: 1145 ExecStart=/home/kubernetes/bin/configure- (code=exited, status=1/FAILURE) Process: 1140 ExecStartPre=/bin/chmod 544 /home/kubernetes/bin/mounter (code=exited, status=0/SUCCESS) Process: 1136 ExecStartPre=/bin/chmod 544 /home/kubernetes/bin/configure- (code=exited, status=0/SUCCESS) Main PID: 1145 (code=exited, status=1/FAILURE)
cc
This is a cluster lifecycle integration issue. I will leave to drive this. cc/ for the support from the node side. Thanks!
Wrong syntax introduced by
analysis was correct. I was able to ssh into my upgraded Kubernetes master, manually edit to fix the shell, unmount the master pd (), and re-run .