kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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

update cloud provider KEPs to implementable status
This commit is contained in:
k8s-ci-robot 2018-11-27 15:33:52 -08:00 committed by GitHub
parent c701c750ac e976ae0970
commit ab65bfbbb5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -19,8 +19,8 @@ approvers:
- TBD - TBD
editor: TBD editor: TBD
creation-date: 2018-06-06 creation-date: 2018-06-06
last-updated: 2018-06-06 last-updated: 2018-11-16
status: provisional status: implementable
--- ---
@ -266,5 +266,6 @@ All providers are periodically uploading conformance test results in at least on
## Implementation History ## 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.

9
keps/sig-cloud-provider/0019-cloud-provider-documentation.md
View File

@ -23,7 +23,9 @@ approvers:
- "@hogepodge" - "@hogepodge"
- "@jagosan" - "@jagosan"
editor: TBD 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 ## 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 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. * 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.