Time-boxed “classroom” OpenShift environment for instructor-led architecture courses

I designed and taught a 6-session course on cloud native and microservices architecture, using the Red Hat Developer Sandbox as the only hands-on environment. The Sandbox is excellent for getting started: free, nothing to install, ready in minutes. But several limits forced me to cut or work around parts of the course:

1. No operators can be installed. OpenShift Service Mesh and AMQ could only be taught on slides, not hands-on.
2. No cluster-admin rights. The NetworkPolicy exercises in the security session could not be done in the shared cluster.
3. Workloads stop after 12 hours. Participants have to redeploy everything at the start of each session.
4. The 30-day trial is shorter than a typical course. Six weekly sessions run past it, so work has to be exported and the environment rebuilt mid-course. I worked around this by keeping every manifest in Git.
5. OpenShift GitOps (Argo CD) availability is uncertain. I had to check it ahead of time before relying on it in the delivery-pipeline session.

My fallback, OpenShift Local, needs 4 cores, 16 GB of RAM and 35 GB of disk on each participant’s laptop. That is often not possible on locked-down corporate machines, especially in the public sector.

Proposal: A time-boxed “classroom” option on Red Hat OpenShift on IBM Cloud, sized for small groups (an instructor plus a few participants). It would include:

• one namespace per participant, with a group owner (the instructor);
• permission to install a curated set of operators (Service Mesh, AMQ Streams, OpenShift GitOps, OpenShift Pipelines) and to apply NetworkPolicy;
• a duration matched to the course (for example 60 to 90 days), with no 12-hour idle shutdown;
• low or zero cost for registered educators and IBM Champions program participants, with automatic teardown at the end.

Who benefits: Instructors, universities and enterprise training teams who teach OpenShift beyond the basics. It shortens the step from “learning OpenShift” to “choosing OpenShift” by letting people try the full platform (mesh, messaging, GitOps), not only the core objects.