Makefile has following variables defined-
KOPS_RELEASE_VERSION=1.6.0-alpha.1
KOPS_CI_VERSION=1.6.0-alpha.2
KOPS_RELEASE_VERSION(1.6.0-alpha.1) is getting picked during 'make' and same is getting populated in kube_env.yaml as protokube image name. However, the pre-build protokube image that is to be used for vSphere cloud provider- https://storage.googleapis.com/kops-vsphere/protokube.tar.gz, has tag 1.6.0-alpha.2 associated with it. So the image name in the nodeup config file- kube_env.yaml and actual image present with docker, running on the master is different.
This is preventing protokube container from getting started, leading to failure of whole deployment.
Makefile has following variables defined- KOPS_RELEASE_VERSION=1.6.0-alpha.1 KOPS_CI_VERSION=1.6.0-alpha.2
KOPS_RELEASE_VERSION(1.6.0-alpha.1) is getting picked during 'make' and same is getting populated in kube_env.yaml as protokube image name. However, the pre-build protokube image that is to be used for vSphere cloud provider- https://storage.googleapis.com/kops-vsphere/protokube.tar.gz, has tag 1.6.0-alpha.2 associated with it. So the image name in the nodeup config file- kube_env.yaml and actual image present with docker, running on the master is different.
This is preventing protokube container from getting started, leading to failure of whole deployment.