Master Platform Engineering, AI Systems, LLMs, and MLOps with comprehensive bootcamps, courses, and hands-on labs
Master HashiCorp Vault from fundamentals to advanced operations across three self-paced modules: Vault fundamentals and certification prep, Kubernetes integration, and enterprise operations. Learn secrets management, Kubernetes integration, enterprise deployment, and prepare for certification. Slots are modules, not calendar weeks. The required path is three courses (~48 hours): Vault 101, Vault 201, and Vault 202. Plan 4-6 calendar weeks at 8-12 hours per week. All modules unlock from day one.
🟡 Beta bootcamp: Content may be refined as we iterate based on student feedback. An 8-week intensive program designed to transition Platform Engineers into AI Platform Engineering and LLMOps roles. Build production-ready AI systems using LLMs, RAG, agents, and MLOps practices on Kubernetes infrastructure. The 8 weeks build toward a capstone Platform Assistant: a production-ready AI system that combines the LLM integration, RAG, agent, MLOps, model serving, and observability layers introduced across each week. Each course advances one layer of that capstone so you finish with a single coherent system, not a pile of disconnected exercises.
🟡 Beta bootcamp: Content may be refined as we iterate based on student feedback. Comprehensive 21-week bootcamp equipping engineers with essential and advanced Platform Engineering and DevOps skills using industry-standard tools and best practices. All 21 weeks share a continuous project called TaskFlow: a full-stack application that grows progressively as you add each new technology. Each week starts from the TaskFlow state produced in the previous week and extends it with the new layer covered in that course (containers, Kubernetes, Terraform, ArgoCD, Vault, Istio, Backstage, and more). By the end you have built and operated a production-grade Internal Developer Platform end to end.
Work through the HashiCorp stack in integration order: Terraform to provision, Packer to bake golden images, Sentinel to govern, Vault to secure, Consul to connect, Nomad to run, then Boundary for identity-aware access. This is a catalog path over existing HashiCorp courses — each course keeps its own lessons and labs. There is no extra combined HashiStack capstone. Slots are modules, not calendar weeks. The required path is six courses (~115 hours): Terraform Associate 004 on AWS, Packer 101, Sentinel 101, Vault Associate 003, Consul 101, and Nomad 101. Plan 10–14 calendar weeks at 8–12 hours per week. Optional Vault 201/202 and Boundary 101 sit on the path but are not required. Labs stay inside each course. For Vault-only depth, take the HashiCorp Vault Security Bootcamp instead.

Build Internal Developer Portals with Backstage and prepare for the CNCF Certified Backstage Associate (CBA) exam

Master HashiCorp Vault fundamentals from basics to advanced concepts and prepare for the Certified Vault Associate exam.
Part of the Platform Engineering Bootcamp. Week 12 of 21. Master Ansible configuration management by automating TaskFlow deployment and server configuration.
Part of the Platform Engineering Bootcamp. Week 10 of 21. Master AWS cloud fundamentals by deploying TaskFlow to AWS infrastructure.

Build Internal Developer Platforms with Crossplane that enable self-service AWS infrastructure provisioning through Kubernetes APIs

Master Terraform 1.14+ through hands-on labs. Build, test, and deploy infrastructure as code with AWS. Prepare for the Terraform Associate 004 certification.
Part of the AI Platform Engineering Bootcamp. Week 4 of 8. The bootcamp follows an 8-week arc that culminates in a capstone Platform Assistant: a production-ready AI system you build by combining the LLM, RAG, agent, MLOps, model serving, and observability layers introduced across each week.
Part of the AI Platform Engineering Bootcamp. Week 1 of 8. The bootcamp follows an 8-week arc that culminates in a capstone Platform Assistant: a production-ready AI system you build by combining the LLM, RAG, agent, MLOps, model serving, and observability layers introduced across each week.
Part of the Platform Engineering Bootcamp. Week 13 of 21. Build internal developer portal using Backstage to improve developer experience.
Hands-on exploration of Cilium components in a running cluster; inspect agent, operator, and CNI configuration.
Connect multiple Kubernetes clusters with Cilium Cluster Mesh, enable cross-cluster service discovery, and implement global policies.
Explore eBPF programs used by Cilium, inspect BPF maps, understand datapath operations, and debug eBPF functionality.
Configure egress gateways for controlled outbound traffic and implement BGP peering for external network integration.
Configure Cilium as a Gateway API implementation, create HTTPRoutes, and manage ingress traffic.
Enable Hubble, use the CLI and UI to observe network flows, troubleshoot connectivity, and monitor application traffic.
Install Cilium on a fresh Kubernetes cluster, configure key options, run connectivity tests, and verify the installation.
Implement HTTP-aware policies, path-based filtering, and method restrictions.
Create L3/L4 policies, test connectivity, implement deny-all baseline, and layer-specific rules.
Short, break-something-fix-it puzzles. Drop into a broken system, diagnose, fix, move on.
The backup cron job "runs" every minute, but no files ever appear. Figure out why and make it work.
A developer submitted a Crossplane claim two hours ago. It is still not Ready. Find out why and fix it.
curl to 1.1.1.1 works, curl to cloudflare.com doesn't. Fix DNS resolution end-to-end.
A pod is CrashLoopBackOff-ing for three different reasons stacked on top of each other. Fix all of them and get it Running.
Ansible deployed TaskFlow's nginx site, but the public check on port 80 fails. Find the wrong listen port and get http://127.0.0.1/ serving TaskFlow OK.
An Argo CD Application sits Unknown/Degraded and never syncs. Find the source misconfiguration and get it Healthy.
Every git commit in this repo fails instantly — even clean ones. Repair the pre-commit hook so good commits land and TODO commits are still blocked.
TaskFlow's Compose stack is up, but the frontend health check can't reach the API. Fix the service name mismatch so /health returns OK.
The Composition is selected and the Claim reconciles, but ConfigMap appconfig-taskflow never appears with the expected data.
Join thousands of students mastering DevOps and Platform Engineering
View Pricing Plans