Phase 1: Common Elements

1. Cloud Development Environment (via Coder)
   • Determine the best machine size (CPU/memory/storage) to support lab scenarios.
   • Provide an isolated Kubernetes cluster inside each environment, accessible solely through a web browser.
   • Set up seamless GitHub authentication.
   • Install and configure essential tools:
     • VS Code (including the Humanitec plugin)
     • kubectl
     • humctl
     • yq / jq
     • opentofu
2. Environment Isolation & Availability
   • Each student’s lab must be isolated from others.
   • Labs remain accessible for at least 12 weeks per cohort.
   • No extra local software needed beyond a browser, ensuring a frictionless experience.

Phase 2: Lab Scenarios

1. Open Source Pipeline-Based
   • Experiment with ArgoCD for CD, Crossplane for infrastructure orchestration, CNOE for setup, and Backstage as a developer portal.
   • Build out example workflows—from Day 1 (bootstrapping apps and environments) to Day 2 (updating configurations, provisioning resources, debugging, rolling back)—to help students see how a fully open-source pipeline-based IDP might work.
2. Proprietary Graph-Based
   • Incorporate Humanitec for platform orchestration (handling both CD and infrastructure) and optionally Cortex as a portal, if available.
   • Provide hands-on labs that let students compare and contrast a proprietary graph-based IDP with the open-source pipeline approach, covering similar Day 1 and Day 2 developer tasks.