Technically correct, or not published
Every command here is written to run as-is, and every explanation is checked against the upstream documentation or source. Where something is genuinely ambiguous, the page says so rather than papering over it.
Why it exists
There is no shortage of Kubernetes content. There is a shortage of content that is simultaneously accurate, current, and honest about where the sharp edges are. Most tutorials stop at kubectl apply and a green checkmark; most reference documentation assumes you already know which page you need.
This site tries to sit in between. The Learn section explains mechanisms — what a Service actually is, what a Deployment actually manages, what config.json actually contains. The Guides section is task-shaped and end to end. The Tools and Resources pages are the things worth keeping close once you already know your way around.
Editorial principles
Explain the mechanism, not just the recipe
Knowing that a ClusterIP is a virtual address maintained by kube-proxy as iptables rules is what lets you debug it. A copy-pasteable YAML block without that context is worth very little at 3am.
Show the failure modes
Most documentation shows the happy path. The interesting part is what breaks: RollingUpdate deadlocking on an RWO volume, ndots:5 quadrupling DNS lookups, a version label leaking into an immutable selector.
No vendor pitch
Nothing here is sponsored and no link is affiliate. Tool recommendations name the licence and link upstream. Where a project is only partly open source, the page says that too.
Contributing
Corrections are the most valuable contribution. If something here is wrong, out of date, or misleading, please open an issue — being wrong in public is only useful if it gets fixed.
- Found an error? Every doc page has an “Edit this page” link at the bottom that takes you straight to the source file on GitHub.
- Want to add a page? CONTRIBUTING.md covers the local setup, file conventions, and the PR checklist.
- Have a question? Open a GitHub Discussion rather than an issue, so the answer stays searchable for the next person.
Accessibility
Accessibility is treated as a build requirement rather than a nice-to-have. Every page uses a single h1 with a correctly nested heading hierarchy, all interactive elements are keyboard reachable with a visible focus ring, decorative graphics are marked aria-hidden, and body text meets WCAG AA contrast in both colour themes. Animations respect prefers-reduced-motion. If you hit something that does not work with your assistive technology, that is a bug worth filing.