End-to-end container platform engineering: OCI runtimes and images with Docker, Podman, Buildah and Skopeo, supply-chain security and signing, then Kubernetes workloads, scheduling, networking, ingress, Helm packaging and enterprise distributions such as K3s, RKE2 and OpenShift. Aligned to CKA, CKAD, CKS, EX180 and EX280 objectives.
Caution
Commands, scripts, labs, and architecture patterns must be validated against current vendor documentation, product versions, licensing, permissions, security policy, and rollback requirements before production use.
- Detailed explanation and architectural context
- Mermaid architecture or workflow diagram
- Commands and reusable automation scripts
- Hands-on lab with explicit validation evidence
- Operational automation and production considerations
- Troubleshooting scenarios and resolutions
- Interview questions with evidence-based answers
- Certification alignment, references, and further-study query
Total: 13 trees · 26 branches · 64 leaves
Level distribution: Advanced: 40 · Beginner: 1 · Enterprise: 1 · Expert: 12 · Intermediate: 10
Browse the complete leaf catalog or start with the first tree above.
- Select a tree based on the operational outcome you need.
- Read prerequisites and scope before executing commands.
- Reproduce the lab in an isolated environment.
- Capture the stated validation evidence.
- Adapt automation only after review, testing, and rollback planning.
Catalog coverage is 100%: all 64 authoritative leaves are present. Coverage indicates documentation completeness, not universal production validation. Product behavior changes across releases and environments.
Read CONTRIBUTING.md before proposing changes. Do not place real credentials, customer data, internal hostnames, or assessment output in issues or pull requests; follow SECURITY.md for sensitive reports.
Licensed under the MIT License. Maintained by @mohamedmahersaid.