Currently I had to manually edit the generated configmap.
We need to update install-config API to enable insecure option for vsphere cloudprovider. I manually edited cloud-config configmap in openshift-config namespace to enable insecure option and which fixed this for me.
The insecure-flag will always be set to 1 by the installer. If the user wants to run securely, then they will need to manually modify the manifest and provide a cert for trust verification.
*** Bug 1699253 has been marked as a duplicate of this bug. ***
Verify this bug with payload 4.1.0-0.nightly-2019-04-22-005054.
# ./openshift-install version
built from commit f3b726cc151f5a3d66bc7e23e81b3013f1347a7e
release image registry.svc.ci.openshift.org/ocp/release@sha256:3f3628cd9b694705cb0627ce72e61932df5d9938a291fabba1ed691230f7b548
After fresh install for upi-on-vsphere, check the cloud-provider-config configmap
# oc get configmap cloud-provider-config -o yaml -n openshift-config |grep insecure-flag
insecure-flag = 1
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.