Merge pull request #2946 from andrewsykim/update-cloud-provider-kep

update cloud provider KEPs to implementable status

keps/sig-cloud-provider/0018-testgrid-conformance-e2e.md

@@ -19,8 +19,8 @@ approvers:
   - TBD
 editor: TBD
 creation-date: 2018-06-06
-last-updated: 2018-06-06
-status: provisional
+last-updated: 2018-11-16
+status: implementable
 
 ---
 
@@ -266,5 +266,6 @@ All providers are periodically uploading conformance test results in at least on
 
 ## Implementation History
 
-- the `Summary` and `Motivation` sections being merged signaling SIG acceptance
+- Jun 6th 2018: KEP is merged as a signal of acceptance. Cloud providers should now be looking to report their conformance test results to testgrid.
+- Nov 19th 2018: KEP has been in implementation stage for roughly 5 months with Alibaba Cloud, Baidu Cloud, DigitalOcean, GCE, OpenStack and vSphere reporting conformance test results to testgrid.
 

keps/sig-cloud-provider/0019-cloud-provider-documentation.md

@@ -23,7 +23,9 @@ approvers:
   - "@hogepodge"
   - "@jagosan"
 editor: TBD
-status: provisional
+creation-date: 2018-07-31
+last-updated: 2018-11-16
+status: implementable
 ---
 ## Transfer the responsibility of maintaining valid documentation for Cloud Provider Code to the Cloud Provider
 
@@ -173,3 +175,8 @@ The Alternatives section is used to highlight and record other possible approach
 * SIG docs could tag cloudprovider documentation as a blocking item for Kubernetes releases
 * SIG docs could also assign SIG-<provider> leads to unblock cloudprovider documentation in the planning phase for the release.
 
+## Implementation History
+
+- July 31st 2018: KEP is merged as a signal of acceptance. Cloud providers should now be looking to add documentation for their provider according to this KEP.
+- Nov 19th 2018: KEP has been in implementation stage for roughly 4 months with Alibaba Cloud, Azure, DigitalOcean, OpenStack and vSphere having written documentation for their providers according to this KEP.
+