Testing your K8s apps with KIND
summary
Kind creates real Kubernetes clusters as Docker containers and boots a single-node cluster in about 30 seconds (multi-node and multi-cluster supported). Tests run hermetically offline by loading Docker images into all nodes instead of pushing to registries, so CI and local runs avoid network flakiness. Used to validate cert-manager API refactors without changing tests, proving backward compatibility. Limitations: IPv6 work-in-progress, Mac/Windows porting caveats, and no Windows nodes yet.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:33What is a Kubernetes application?
- 2:06Defining types of test
- 6:52Why end-to-end tests?
- 9:12Introducing kind
- 10:22kind as a testing tool
- 10:38Boot cluster
- 11:11Passing additional config
- 11:41HA control planes
- 11:56Advanced networking config
- 12:08Sideload Application Images
- 12:46Run your tests!
- 12:57Demo time
- 17:41Running in CI
- 19:13What's Next?
related talks
31mDeep Dive: Kind
29mKubernetes Advanced Networking Testing with KIND
30mTechniques and Insights To Test Kubernetes Limits With Kind
01h 00mJava on Kubernetes What I Wish I Knew First
24mCYOK - Choose Your Own Kubernetes For Local Development
45mKubernetes Local Development Workflow Distilled
26mIntegration testing for container images via Kind in GitLab CI
16mWhy Kubernetes Applications Require a New Approach to Testing using Testkube