keps: Begin beta graduation requirements for controller manager

Mostly just propose a repository structure for existing providers
and punt on the details of accepting new cloud providers

keps/0002-controller-manager.md

@@ -267,9 +267,52 @@ Hopefully the content previously contained in [umbrella issues][] will be tracke
 
 [umbrella issues]: https://github.com/kubernetes/kubernetes/issues/42752
 
+### Graduation to Beta
 
+As part of the graduation to `stable` or General Availability (GA), we have set
+both process and technical goals.
 
+#### Process Goals
 
+- 
+
+We propose the following repository structure for the cloud providers which
+currently live in `kubernetes/pkg/cloudprovider/providers/*`
+
+```
+[email protected]:kubernetes/wg-cloud-provider
+[email protected]:kubernetes/aws-cloud-provider
+[email protected]:kubernetes/azure-cloud-provider
+[email protected]:kubernetes/cloudstack-cloud-provider
+[email protected]:kubernetes/gce-cloud-provider
+[email protected]:kubernetes/openstack-cloud-provider
+[email protected]:kubernetes/ovirt-cloud-provider
+[email protected]:kubernetes/photon-cloud-provider
+[email protected]:kubernetes/vsphere-cloud-provider
+```
+
+We propose this structure in order to obtain
+
+- ease of contributor on boarding and off boarding by creating repositories under
+  the existing `kubernetes` GitHub organization
+- ease of automation turn up using existing tooling
+- unambiguous ownership of assets by the CNCF
+
+The use of a tracking repository `[email protected]:kubernetes/wg-cloud-provider`
+is proposed to
+
+- create an index of all cloud providers which WG Cloud Provider believes
+  should be highlighted based on defined criteria for quality, usage, and other
+  requirements deemed necessary by the working group
+- serve as a location for tracking issues which affect all Cloud Providers
+- serve as a repository for user experience reports related to Cloud Providers
+  which live within the Kubernetes GitHub organization or desire to do so
+
+The ultimate intention of WG Cloud Provider is to prevent multiple classes
+of software purporting to be an implementation of the Cloud Provider interface
+from fracturing the Kubernetes Community while also ensuring that new Cloud
+Providers adhere to standards of quality and whose management follow Kubernetes
+Community norms.
 
 ## Alternatives