manifests: add cloudproviderconfig asset

[abhinavdahiya]

This configuration file is used to configure the Kubernetes cloud provider integration
when using the built-in cloud provider integration or the external cloud controller manager.

The configmap containing cloud provider config must be in openshift-config namespace as required by openshift/api PR 245 1

/cc @staebler @derekwaynecarr
This should help plumb the vsphere cloud provider config whenever that becomes ready.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [abhinavdahiya]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@abhinavdahiya: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws	9c118a6	link	/test e2e-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[derekwaynecarr]

Hold until @gnufied and I have a chance to sync up this week.

[gnufied]

@derekwaynecarr I double and triple checked storage bits for vsphere and traditionally in openshift-ansible when we configure vsphere cloudprovider, naturally you specify a datastore too. But - it is not mandatory to have datastore specified in storageclass and storagelclass will simply default to datastore configured in current workspace.

So, in a nutshell - we don't need anything beyond platform being set to vSphere. After that, if controller-manager is configured correctly, everything should work as expected. I am sorry that, my earlier assumption about this was not entirely correct. but like I said - I am 100% certain now that, we aren't going to need anything for configuring default storageclass.

[sjenning]

fyi @rphillips

[openshift-ci-robot]

@abhinavdahiya: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sdodson]

/close
rolled into #1516

[openshift-ci-robot]

@sdodson: Closed this PR.

Details

In response to this:

/close
rolled into #1516

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.