Prerequisites
Basic computer literacy and a willingness to document experiments.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- API server, scheduler and controllers
- Pods, ReplicaSets and Deployments
- Namespaces and labels/selectors
- kubectl and manifest structure
- Kubernetes specialization: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Tools
Kuberneteskubectlkind or minikube
Hands-on exercise
Deploy a simple workload in a local cluster and inspect the object lifecycle. Context for this route: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Suggested project
A versioned manifest set with namespace boundaries. The outcome must directly demonstrate Kubernetes, not merely list tools.
Learning resources
Completion criteria
You can explain the reconciliation loop and desired state. Evidence must be reproducible and tied to Kubernetes.
Next: Services, DNS & ingress
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- ClusterIP, NodePort and LoadBalancer
- CoreDNS and service discovery
- Ingress and Gateway concepts
- Network policies
- Kubernetes specialization: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Tools
kubectlIngress controllerLocal cluster
Hands-on exercise
Expose two services and verify that only the intended route is reachable. Context for this route: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Suggested project
A multi-service app with documented traffic paths. The outcome must directly demonstrate Kubernetes, not merely list tools.
Learning resources
Completion criteria
Service discovery and ingress rules behave as designed. Evidence must be reproducible and tied to Kubernetes.
Next: Configuration, secrets & storage
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- ConfigMaps and Secrets
- PersistentVolumes and claims
- Storage classes
- Secret encryption and external secret patterns
- Kubernetes specialization: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Tools
Kubernetes manifestsCSI conceptsSecret manager
Hands-on exercise
Attach a persistent volume and rotate a test credential without rebuilding the image. Context for this route: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Suggested project
A stateful workload with safe configuration management. The outcome must directly demonstrate Kubernetes, not merely list tools.
Learning resources
Completion criteria
State remains available after pod replacement and secrets are not committed. Evidence must be reproducible and tied to Kubernetes.
Next: Scheduling, scaling & resilience
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Requests, limits and QoS
- Probes and disruption budgets
- HPA and cluster autoscaling
- Affinity, taints and tolerations
- Kubernetes specialization: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Tools
Metrics ServerkubectlLoad generator
Hands-on exercise
Introduce load and observe scaling and pod rescheduling. Context for this route: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Suggested project
A resilient deployment with resource budgets and scaling policy. The outcome must directly demonstrate Kubernetes, not merely list tools.
Learning resources
Completion criteria
The workload recovers predictably under a documented failure test. Evidence must be reproducible and tied to Kubernetes.
Next: RBAC, policy & cluster hardening
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- RBAC roles and service accounts
- Pod security standards
- Network policies and admission control
- Audit logs and image provenance
- Kubernetes specialization: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Tools
RBAC manifestsPolicy engineImage scanner
Hands-on exercise
Create a limited service account and prove it cannot modify unrelated resources. Context for this route: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Suggested project
A cluster security baseline with least-privilege roles. The outcome must directly demonstrate Kubernetes, not merely list tools.
Learning resources
Completion criteria
Permissions are scoped and risky container settings are rejected. Evidence must be reproducible and tied to Kubernetes.
Next: Observability & troubleshooting
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Events, logs and resource metrics
- Control-plane and node diagnostics
- Tracing and service-level indicators
- Alert quality and runbooks
- Kubernetes specialization: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Tools
PrometheusGrafanakubectl debug
Hands-on exercise
Break one dependency and trace the failure from alert to root cause. Context for this route: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Suggested project
A cluster dashboard and troubleshooting runbook. The outcome must directly demonstrate Kubernetes, not merely list tools.
Learning resources
Completion criteria
The runbook identifies the failed layer and a safe remediation. Evidence must be reproducible and tied to Kubernetes.
Next: GitOps & release lifecycle
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Helm/Kustomize and overlays
- GitOps reconciliation
- Progressive delivery
- Backup and restore for cluster state
- Kubernetes specialization: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Tools
Helm or KustomizeArgo CD or FluxGit
Hands-on exercise
Promote a change from test to staging and roll it back through Git history. Context for this route: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Suggested project
A GitOps repository with environment overlays and release policy. The outcome must directly demonstrate Kubernetes, not merely list tools.
Learning resources
Completion criteria
Cluster state converges from versioned configuration. Evidence must be reproducible and tied to Kubernetes.
Next: Capstone: reliable Kubernetes service
Prerequisites
Completion of the previous stage and a working local practice environment.
Learning objectives
- Explain the stage-specific model and its limits
- Apply the listed concepts using a controlled exercise
- Record results, failure cases and a reproducible evidence trail
Topics to learn
- Architecture and resource sizing
- Network/storage and identity
- Policy and security posture
- SLO, release and recovery
- Kubernetes specialization: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Tools
KubernetesHelm/GitOpsMonitoring
Hands-on exercise
Run a controlled pod failure and rollout rollback, then provide evidence. Context for this route: Kubernetes: focus on controllers, Services/Ingress, ConfigMaps/Secrets, storage, probes, RBAC and GitOps.
Suggested project
A multi-component cluster deployment with dashboards, policies and runbooks. The outcome must directly demonstrate Kubernetes, not merely list tools.
Learning resources
Completion criteria
The service meets its stated availability and security objectives in tests. Evidence must be reproducible and tied to Kubernetes.
End of roadmap: Complete the final project and build your portfolio.