-
Verify that the list of files matches the expected list.
-
Note the
vX.Y
subdirectory that the PR is in, this is the version of Kubernetes for which conformance is being claimed, referenced as the "Conformance Version" from hereon. -
Verify that the Conformance Version is the current or previous two versions of Kubernetes.
-
Look at
e2e.log
. Verify that themajor.minor
component of thekube-apiserver version:
log ande2e test version:
both exactly match the Conformance Version. The patch version does not matter. -
Verify that the last line of
e2e.log
says "SUCCESS! --N
Passed | 0 Failed | 0 Pending |M
Skipped PASS". The exact value ofN
andM
don't matter as long as we see0 Failed | 0 Pending
. Also, there should be 0 tests listed asFlaked
. -
Verify that no files outside of the submitted subdirectory are being modified. For example, if a submission is adding files to
https://github.com/cncf/k8s-conformance/tree/master/v1.18/coyote/
, ensure that it doesn't changehttps://github.com/cncf/k8s-conformance/blob/master/README.md
orhttps://github.com/cncf/k8s-conformance/tree/master/v1.18/roadrunner/
.
- Confirm that the vendor is currently a member of CNCF. If they are not, request that they reach out to [email protected] to become a member in order to complete their certification. (Companies can alternatively pay a certification fee equal to the cost of membership if, for whatever reason, they don't wish to become a CNCF member.) Alternatively, non-profit organizations (including community distributions like Debian) can certify at no cost.
Review the PRODUCT.yaml
file, and:
-
Verify that there is a Participation Form on file for the
vendor
, and that the vendor is in good standing in the program. -
Verify the product
name
andwebsite_url
are listed in the "Qualifying Offerings" section of the vendor's Participation Form, i.e. that thename
andwebsite_url
are listed. -
Review the
name
. If it contains the word "Kubernetes" in a non-descriptive fashion, verify that thename
is listed in "Participant Kubernetes Combinations" section of the vendor's Participation Form.
If the submission doesn't meet all policy requirements, reply with a message indicating "Signed participation form needed", "Files missing from PR", "Membership in CNCF or confirmation of non-profit status needed", etc.
-
Update the Kubernetes Distributions & Platforms spreadsheet to reflect the vendor's certified offering.
-
Add the vendor's information to the CNCF landscape which also causes them to appear on https://www.cncf.io/certification/software-conformance/ and https://kubernetes.io/partners/#conformance.
-
Add a comment saying "You are now Certified Kubernetes" and merge the PR.