From 26db528da30bfbfe0071616cf79efa6fc0c7299c Mon Sep 17 00:00:00 2001
From: Ritesh H Shukla <sritesh@vmware.com>
Date: Mon, 17 Oct 2016 23:42:59 +0000
Subject: [PATCH] Fix panic in vSphere when deploying on a single ESX node.

Use ComputeResource instead of ClusterComputeResource when
initializing the vSphere Cloud Provider
---
 pkg/cloudprovider/providers/vsphere/vsphere.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pkg/cloudprovider/providers/vsphere/vsphere.go b/pkg/cloudprovider/providers/vsphere/vsphere.go
index 1ecb49ccd03..a3dae8e1d9c 100644
--- a/pkg/cloudprovider/providers/vsphere/vsphere.go
+++ b/pkg/cloudprovider/providers/vsphere/vsphere.go
@@ -252,7 +252,7 @@ func readInstance(cfg *VSphereConfig) (string, string, error) {
 		var rp mo.ResourcePool
 		err = s.Properties(ctx, *vm.ResourcePool, []string{"parent"}, &rp)
 		if err == nil {
-			var ccr mo.ClusterComputeResource
+			var ccr mo.ComputeResource
 			err = s.Properties(ctx, *rp.Parent, []string{"name"}, &ccr)
 			if err == nil {
 				cluster = ccr.Name