DEV106 · Container Orchestration with Kubernetes
About Course
Run containerized applications reliably with Kubernetes: deployments, services, configuration, health probes, scaling and safe updates. You will deploy a web API and database to a local cluster and practice rolling updates and rollbacks.
Who it is for
Developers and operations staff who can build containers and need to run them at scale with self-healing and zero-downtime updates.
Prerequisites
Complete DEV105 or be comfortable building Docker images and using Docker Compose.
What you will be able to do
- Explain the Kubernetes architecture and the role of pods, deployments, services and namespaces.
- Deploy an application declaratively with YAML manifests and kubectl.
- Configure applications with ConfigMaps, Secrets, resource requests and health probes.
- Perform rolling updates, rollbacks and autoscaling, and apply basic cluster security practices.
Lessons
- Lesson 1 · Kubernetes architecture and core objects
- Lesson 2 · Networking, configuration and health
- Lesson 3 · Updates, scaling, storage and security
- Lesson 4 · Lab and assignment
Lab: Deploy an API to a local Kubernetes cluster
You will create a local cluster with kind, deploy a Node.js API with three replicas and a PostgreSQL database with persistent storage, and expose the API through a Service and an Ingress. You will add probes and resource limits, perform a rolling update, roll it back and watch the cluster replace a deleted pod automatically.
Free tools: kind or minikube (free, running in Docker Desktop), kubectl, Helm, VS Code with the Kubernetes extension and the free k9s terminal UI (optional)
Assessed assignment
Deploy a small business application, such as a restaurant reservation API or a gym check-in service, to a local Kubernetes cluster. Provide manifests or a Helm chart for a namespace, a Deployment with at least two replicas, a Service, an Ingress, a ConfigMap, a Secret, readiness and liveness probes, resource requests and limits, a database with a PersistentVolumeClaim and a HorizontalPodAutoscaler. Document a rolling update and a rollback with command output, and write a short note on which security settings you applied and why.
| Criterion | Weight | What excellent work looks like |
|---|---|---|
| Manifest correctness | 30% | All resources apply cleanly, use labels and selectors consistently and reflect the documented architecture. |
| Reliability features | 25% | Probes, resource settings, replicas and persistent storage are configured sensibly and demonstrated. |
| Updates and scaling | 25% | The rolling update, rollback and autoscaling are shown with evidence and explained. |
| Security and documentation | 20% | Secrets are handled properly, containers run as non-root, and the README explains how to deploy and remove everything. |
Portfolio piece
A set of Kubernetes manifests or a Helm chart that runs a small business application with probes, scaling and documented updates.
Next step
Continue with DEV107 · Infrastructure as Code with Terraform · 8 hours · $56.00
Course Content
DEV106 · Container Orchestration with Kubernetes (8 h)
-
Lesson 1 · Kubernetes architecture and core objects
-
Lesson 2 · Networking, configuration and health
-
Lesson 3 · Updates, scaling, storage and security
-
Lesson 4 · Lab and assignment
-
DEV106 Assessment · Container Orchestration with Kubernetes