Intro + Deep Dive: Kubernetes Conformance WG
summary
Kubernetes conformance program (launched 2017) claims 84 certified partners and uses an in-cluster tester called son a boy status that schedules the end-to-end suite inside the cluster, typically taking ~60–180 minutes and producing logs like “200 passed no failed.” API Snoop surfaces gaps: ~95 stable core endpoints used in release-blocking jobs lack tests and ~125 endpoints are only hit by core components. Validation suites and SIG-driven test promotion aim to close those gaps; Windows node behaviors are triaged as linux-only where needed.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:4184 Certified Kubernetes Partners
- 4:07Why we created this
- 5:35Benefits
- 6:31Why Certify?
- 7:24Conformance Ownership
- 14:05Adding Tests to 1.14
- 22:06API Coverage
- 23:22GitHub Activity
- 27:32Sources
- 35:02APISnoop
- 53:56Conformance Process
- 54:27Test Development
related talks
32mIntro + Deep Dive: Kubernetes Conformance WG
32mIntro + Deep Dive: Kubernetes Conformance WG
36mKubernetes Conformance WG Intro – William Denniss
27mAdventures in Conformance
27mIntro: CNCF K8s-Conformance WG
35mK8s Conformance & SIG Architecture Conformance Subgroup
16mContributing to Kubernetes Conformance Coverage
20mConformance Testing the Kubernetes API: Tooling that Makes the Difference
