Kubernetes Production Bootcamp
Eight live sessions that take you from a cluster that runs to a platform you can be on call for: rollouts, traffic, secrets, storage, observability and security.
Run Kubernetes in production without guessing
Eight live Saturday sessions with a real cluster in front of you: rollouts that keep serving traffic, requests you can trace end to end, secrets that stay out of git, and enough observability to know before your users do.
What you will be able to do by week eight
- Ship a workload with probes, resource requests and a rollout strategy you can defend in review.
- Expose a service through Ingress and explain the path a request takes to your pod.
- Keep configuration and credentials out of your images and out of your git history.
- Run a stateful workload on persistent storage and survive a node restart.
- Read a cluster's metrics and logs, and write one alert worth waking up for.
- Lock a namespace down with RBAC and network policy without breaking the application.
- Rehearse a cluster upgrade before you do it to production.
Who this bootcamp is for
- Backend and platform engineers who are already shipping containers and now own the cluster.
- System administrators and SREs moving workloads from virtual machines to Kubernetes.
- DevOps engineers who learned kubectl from tutorials and want the production half.
- Engineers who have passed a Kubernetes exam but have never been on call for a cluster.
What you need before week one
- Comfort on the Linux command line: files, processes, systemd, journalctl.
- You have built and run a container image and know what a registry is.
- kubectl installed locally — every lab itself runs in the browser on our clusters.
- About three hours a week outside the live sessions for the labs.
The eight weeks
One live session a week, each followed by a hands-on lab on a cluster we create for you. This is the cohort's real schedule, not a sample.
Every week ends on a real cluster
Labs run in the browser on clusters we create for you — nothing to install, nothing to pay a cloud provider for. Your cohort seat includes them for the length of the bootcamp; you do not need a separate subscription.
Break it, then fix it
Most labs start from a cluster that is already failing, because that is the state you will meet at work.
Your own namespace
Each participant gets an isolated namespace with real resource limits, so noisy neighbours are part of the lesson.
Checked, not just completed
Labs are graded against the cluster's actual state, so a lab passes because the workload is healthy, not because you ran the commands.
Reviewed in the next session
The following week opens with what the cohort got stuck on, so the labs feed the teaching rather than sitting beside it.
How the bootcamp runs
Live, not pre-recorded
Eight Saturday sessions of two and a half hours, taught live in Arabic. You can interrupt, and people do.
Recordings you keep
Every session is posted to the cohort workspace, usually within a day, and stays available to you after the cohort ends.
A cohort workspace
Schedule, prep notes, recordings, slides and lab links for your cohort in one place, with your own attendance and progress.
Small by design
25 seats. Applications are read individually, and a cohort that would not work for you is a rejection, not a sale.
One price, everything included
The price shown is for your market. A 30% deposit reserves your seat and the balance is due by session three. The seat covers the eight live sessions, the labs and the recordings — there is nothing else to buy.
Questions applicants ask
Take one of the 25 seats
Applications for the October 2026 cohort close on 26 September, or when the seats are gone. It takes about five minutes to apply.
EGP 18,000.00
Starts Oct 3, 2026, 7:00 PM