Contributing to Kubernetes Conformance Coverage - Zach Mandeville & Caleb Woodbine, ii.coop

The presentation discusses how to improve Kubernetes coverage through identifying gaps, writing and promoting tests, and preventing new gaps from forming with release blocking jobs.

• Use API snoop and snoop db to identify gaps in Kubernetes coverage
• Write and promote tests to close gaps
• Prevent new gaps from forming with release blocking jobs
• Conformance ensures that every vendor's version of Kubernetes supports the required APIs
• Strong ecosystem around conformance supporting all levels of involvement with Kubernetes

The presentation includes a demo of how to write tests using sharing.io to create clusters on the fly and deploy applications for easy pairing and sharing. The demo shows how to identify an untested feature using API snoop, write a mock test for it, and then convert it into an actual EDE test that can be submitted as a PR. The entire process is automated and includes auditing of results and release blocking jobs to prevent new gaps from forming.

In this session we'll walk through the Certified Kubernetes program (cncf.io/ck) followed by a deep-dive into the tooling developed for identification, removal and prevention of gaps in certification test coverage.In the intro, we will cover the steps required to become a CNCF Certified Kubernetes provider.We will also deep dive into the APISnoop technologies supporting conformance, specifically:- Identifying Gaps (apisnoop.cncf.io) Closing Gaps (apisnoop audit sink + test writing w/ humacs.org) Preventing Gaps (release blocking w/ prow.k8s.io) Verifying cloud provider submissions (prow.cncf.io)