Filling the Gaps in Kubernetes Test Coverage
summary
Historical cluster audits show only 11% of Kubernetes API usage hit e2e tests, leaving large gaps across roughly 1,400 endpoints. The demo uses apisnoop plus kube audit logs, the Kubernetes e2e test suite and kind to spin a local cluster with audit registration, feeding logs into test-grid and a queryable site that highlights untested endpoints. The CNCF conformance policy now requires GA features to have tests, apisnoop surfaces missing coverage, and the tooling (despite demo glitches) successfully identifies where tests must be added.
AI-written summary · about
chapters (6)
related talks
20mFilling the Gaps in Kubernetes Test Coverage - Hippie Hacker, ii.coop
20mConformance Testing the Kubernetes API: Tooling that Makes the Difference
16mContributing to Kubernetes Conformance Coverage
34mKubernetes Conformance Deep Dive
23mContributing to Kubernetes Conformance Coverage
01h 27mIntro + Deep Dive: Kubernetes Conformance WG
32mIntro + Deep Dive: Kubernetes Conformance WG
36mKubernetes Conformance WG Intro – William Denniss
