luomiao
commented
7 years ago This is the same to the one you just merged into Sandeep's repo rt? Then I think you can directly merge it :)
Closed prashima closed 7 years ago
luomiao
commented
7 years ago This is the same to the one you just merged into Sandeep's repo rt? Then I think you can directly merge it :)
Changes:
Added vsphere_volume to handle static volumes for vSphere VM and update protokube/main.go to identify vSphere cloud. Added cluster-id flag in protokube flags and populating it for vSphere, in order to pass cluster name to protokube. Added make file target to help build and push nodeup and protokube binary/image in vSphere VM and docker registery, respectively. Added doc for vSphere related development and hacks for nodeup and protokube testing. Testing:
Successfully ran make for 'ci' and 'push-vsphere' targets. Manual testing of nodeup and protokube binaries on standalone vSphere VM. Safety: These changes are not being executed for any workflows for any cloud providers, unless tried explicitly by updating cluster.spec and executing nodeup.
With these changes 2 statically mounted disks on vSphere VMs can be used by protokube for etcd data and etcd event storage purpose. End-to-end kubernetes configuration is not working on standalone VM for following reasons:
Error while applying master taints: Eg: 'kube_boot.go:117] error updating master taints: error querying nodes: Get http://localhost:8080/api/v1/nodes?labelSelector=kubernetes.io%2Frole%3Dmaster: dial tcp [::1]:8080: getsockopt: connection refused' Code is not able to access various namespaces. Eg: 'error querying namespace "kube-system": Get http://localhost:8080/api/v1/namespaces/kube-system: dial tcp [::1]:8080: getsockopt: connection refused'