Fix kube vsphere.kerneltime

[kerneltime]

What this PR does / why we need it:
This fixes kube-up to correctly install and configure on vSphere and avoid panics when only a single ESX(hypervisor) is used instead of a cluster.

Which issue this PR fixes
fixes #34992
fixes #34847

Fix kube vsphere.kerneltime

Special notes for your reviewer:

We plan to cherry pick this into 1.4 release branch as well Ref: #34993

---

This change is

[pdhamdhere]

LGTM.

[kerneltime]

cc @dagnello @imkin @abrarshivani @luomiao

[zmerlynn]

This doesn't look like the same set of changes you had in #34993. Were those changes already in another PR? If so, you'll need to cherry-pick them both (and you may want to note that on the other PR).

https://github.com/kubernetes/kubernetes/blob/master/docs/devel/cherry-picks.md

[k8s-cherrypick-bot]

Removing label cherrypick-candidate because no release milestone was set. This is an invalid state and thus this PR is not being considered for cherry-pick to any release branch. Please add an appropriate release milestone and then re-add the label.

[kerneltime]

@zmerlynn Those changes are already part of the master. So with these 2 commits the master will have all the commits that were part of #34993
I will then cherry pick all the changes from master into release 1.4

A longer explanation, #34993 was a combination of 3 cherry-picks and 2 new commits. Thus, when targeting the change for master I only need 2 commits (here) since the 3 were already in (#31467)

[kerneltime]

Understood. This PR does need to be cherry picked. I will request the other PR (#31467) to be cherry picked as well. Thank you!

[kerneltime]

@zmerlynn Do I comment on #31467 to have it cherry-picked or do I start a new PR? Sorry for the confusion.

[imkin]

@kerneltime "cherrypick-candidate" and milestone 1.4 should suffice I believe. Once the tests pass adding a cherrypick-approved will tag this for cherrypicking into 1.4 release

[kerneltime]

For #31467 and this PR I do not have ability to change labels or tag..

[roberthbailey]

@kerneltime if you can't add labels, please request that your reviewer add them for you.

[zmerlynn]

@kerneltime: After this PR gets merged and cherrypick approved, you can propose the cherrypick yourself (see the link from #34997 (comment)). You can roll multiple PRs into one cherrypick, so in this case, you'd do e.g.:

hack/cherry_pick_pull.sh upstream/release-1.4 31467 34997

This PR should go in shortly. I labeled it as retest-not-required since we have no PR-builder coverage for vSphere (yet), so the submit queue should pick it up next pass.

[kerneltime]

@zmerlynn Got it. Thank you!

[k8s-github-robot]

Automatic merge from submit-queue

[kerneltime]

Cherry pick PR #35059