Practical learning · 9 projects
DevOps: Git, Docker, Kubernetes and CI/CD: projects and labs
Learn by doing: labs for each module, a project for each level, a capstone and a project exam. Every step is checked, and your work stays on this device.
Beginner
- Lab1.5 h · 5 stepsLab: DORA metrics for a UPI app teamThe PayKaro UPI app team wants to know if its delivery is getting better. You turn two weeks of its pipeline export into the four DORA keys (deployment frequency, lead time for changes, change failure rate and time to restore) and a one-line report for the weekly review.Not started
- Lab1.5 h · 5 stepsLab: a health check for a clinic booking serverA small clinic in Nashik takes appointment bookings on a Linux server. You find the failing requests in its web log with text tools, write a bash health-check script, run it against a local web service, schedule it with cron, and prove it reports a failure when the service stops.Not started
- Lab1.5 h · 5 stepsLab: version a college fee-receipt config with GitThe accounts office of a college keeps its fee rules in a small config file that two clerks edit. You put it under Git, add a change on a feature branch, resolve a real merge conflict between two clerks' edits, undo a bad change safely with revert, and tag the first release.Not started
- Lab2 h · 5 stepsLab: containerise a kirana shop's price APISharma Kirana wants its price list on a small web API that runs the same on any machine. You write a Dockerfile that builds a non-root image, run it with a port mapping, keep its data in a named volume across container restarts, and push it to a local registry.Not started
- Project4 h · 7 stepsProject: a society notice board with Docker ComposeGreen Park Co-operative Housing Society wants its notices (water cuts, maintenance dues, meetings) on a small web API. You keep the code in Git, build a cached, non-root image, describe the API and its Redis database in one compose.yaml with health checks and a volume, prove the data survives a restart, and tag a release whose version reaches the image name.Not started
Expert
- Project6 h · 8 stepsProject: monitor and secure a clinic appointments APIArogya Clinic's booking API sometimes fails when its SMS gateway is flaky. You scan its image before release, scrape it with Prometheus, measure the failures with PromQL, write and test an alert rule, watch it fire, work out the error budget and burn rate for its SLO in JavaScript, and write the blameless postmortem.Not started
- Capstone14 h · 12 stepsCapstone: a canteen order API from commit to monitored productionBuild the whole delivery path for a college canteen's order API. You write and test the order maths, keep the code on GitHub, package it as a non-root image, let GitHub Actions test, scan and publish it to GHCR, create the namespace and settings with Terraform, deploy it to Kubernetes with probes and limits, release v1.0.0, and watch it with Prometheus and an alert you have seen fire.Not started
- Project exam2.5 h · 11 tasksProject exam: DevOps practicalA timed, hands-on exam for a small college results service. In two and a half hours you analyse a log, version the code, build and run a non-root image with a health check, deploy it to Kubernetes with settings, update and roll it back, make CI pass, manage a file with Terraform, and write two release tools in JavaScript. Every task is checked; no hints or answers are shown until you hand in.Not taken