Errors
Search for the exact text you’re looking at. Every page follows the same order: what it means, how to diagnose it, the usual causes, and the fix.
How these pages are checked
Section titled “How these pages are checked”Every error message on these pages is a real one. Each page links to the exact line in the upstream source code that produces the message, pinned to a release (Kubernetes pages are checked against v1.37.2), plus the official documentation for the fix. Where a message changed between releases, the page shows both wordings.
What isn’t done yet: running every example on a live cluster. Pages say “Draft” at the top until someone has, and then list the versions they were tested on.
By technology
Section titled “By technology”Kubernetes: Pod, scheduling, storage, networking, access, rollout, and control plane errors.
Planned
Section titled “Planned”Linux: Disk full, out of memory, permission denied, and failing systemd units.
Docker and containers: Build failures, image pull errors, and containers that exit immediately.
OpenShift: Degraded cluster operators, SCC denials, and stuck upgrades.
GitLab CI: Stuck jobs, runner errors, and failed deployments from pipelines.