Bug 1530225

Description of problem:

After upgraded to 3.9, atomic-openshift-master-controllers reported an error:

```
Jan  2 16:09:07 ocp38 atomic-openshift-master-controllers: F0102 16:09:07.169092   27717 client_builder.go:273] ServiceAccount "vSphere-cloud-provider" is invalid: metadata.name: Invalid value: "vSphere-cloud-provider": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
```

Just a minute ago it was functional in 3.8.


Version-Release number of selected component (if applicable):
openshift v3.9.0-0.9.0
kubernetes v1.8.1+0d5291c
etcd 3.2.8

How reproducible:
Always

Steps to Reproduce:
1.  Configure OCP 3.9, enable vSphere cloud provider
2. Create StorageClass and PVC
3. Check atomic-openshift-master-controllers log

Actual results:
2. PV can not be provisioned
3. Log:

```
Jan  2 17:57:45 ocp38 atomic-openshift-master-api: I0102 17:57:45.233890   38287 wrap.go:42] GET /api/v1/namespaces/kube-system/serviceaccounts/vSphere-cloud-provider: (3.872489129s) 404 [[openshift/v1.8.1+0d5291c (linux/amd64) kubernetes/0d5291c/controller-manager] 10.66.146.129:59634]
Jan  2 17:57:45 ocp38 atomic-openshift-master-controllers: F0102 17:57:45.505886   40790 client_builder.go:273] ServiceAccount "vSphere-cloud-provider" is invalid: metadata.name: Invalid value: "vSphere-cloud-provider": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
```

There is no such service account "vSphere-cloud-provider".
# oc get serviceaccounts -n kube-system 
NAME                         SECRETS   AGE
attachdetach-controller      2         12d
builder                      2         12d
certificate-controller       2         12d
cronjob-controller           2         12d
daemon-set-controller        2         12d
default                      2         12d
deployer                     2         12d
deployment-controller        2         12d
disruption-controller        2         12d
endpoint-controller          2         12d
generic-garbage-collector    2         12d
job-controller               2         12d
namespace-controller         2         12d
node-controller              2         12d
persistent-volume-binder     2         12d
pod-garbage-collector        2         12d
replicaset-controller        2         12d
replication-controller       2         12d
resourcequota-controller     2         12d
service-account-controller   2         12d
service-controller           2         12d
statefulset-controller       2         12d



Expected results:
vSphere cloud provider is functional.

Additional info: