How alijahnas/cka-practice-exercises works
Project Type and Purpose
• This repo is an educational/infrastructure-as-code project to practice for the Certified Kubernetes Administrator (CKA) exam.
• Its main “runtime” is a Kubernetes cluster you provision, configure, and exercise against.
File Structure
• Top-level scripts and docs:
– containerd-install.sh: bootstrap container runtime
– *.md files: exercise modules for each CKA domain
• terraform/ : IaC definitions (cluster-infra.tf)
• Supporting docs: troubleshooting.md, services-networking.md, storage.md, workloads-scheduling.md, cluster-architecture-installation-configuration.md
README
• Explains the five exam domains and links to each module.
• Encourages use of “Kubernetes the Hard Way” and official docs.
• Describes exam workflow: multiple clusters, CLI-first, time-boxed.
Main Components
a. Infrastructure Provisioning (Terraform)
• Cloud VPC/Network
• Master and Worker VMs (compute instances)
b. Base OS + Container Runtime
• containerd (installed via containerd-install.sh)
c. Kubernetes Cluster
• Control Plane (kube-apiserver, etcd, controller-manager, scheduler)
• Worker Nodes (kube-let, kube-proxy)
d. Exercise Modules (Mapping to K8s constructs)
• Cluster Architecture & Installation (bootstrap flows)
• Workloads & Scheduling (Deployments, Pods, DaemonSets)
• Services & Networking (Services, Ingress, CNI plugin)
• Storage (PersistentVolume, StorageClass)
• Troubleshooting (kubectl, logs, events)
e. External Dependencies
• Official Kubernetes docs (kubernetes.io)
• Container registry (e.g., Docker Hub)
Relationships and Interactions
• Terraform → provisions VMs & network
• VMs → run containerd (via install script) → enable kube-adm or manual kube-let
• Control Plane ↔ Worker Nodes communicate over CNI
• kubectl (on admin workstation) ↔ kube-api server for exercises
• Workloads ↔ Services ↔ Networking plugin
• Workloads ↔ PVs (storage backend)
• Troubleshooting uses logs, events, exec into pods
Architectural Patterns & Principles
• Declarative IaC for infra (Terraform HCL)
• Immutable nodes with containerd + kubeadm bootstrap
• Modular “exercise” documentation separated by domain
• Layered architecture: Infra → Platform → Workloads → Observability
Technologies & Frameworks
• Terraform (IaC)
• containerd, kubeadm, kube-let, kube-proxy
• Kubernetes CNI (e.g., Calico, Flannel)
• YAML manifests for K8s resources
• Bash scripts for automation
Putting It All Together
• On the left, show Terraform & containerd-install.sh driving VM creation & bootstrap.
• Provisioning → Bootstrap → Operations (kubectl → API)
• Data flow between pods, services, and storage.
Detail Without Over-Complexity
• Layer explicitly but avoid drawing every single Kubernetes micro-service.
• Modules, the IaC → cluster → exercises flow, and the exam-style interaction via kubectl.