EduShell
architecturekubernetesinfrastructure

Topologies, not sandboxes

The EduShell team · July 25, 2026 · 2 min read

The promise of a hands-on lab comes down to one word: do. Not watch a video, not paste commands into a throwaway terminal, but operate a system that looks like the one you'll meet in production. This is where most platforms stop too early.

The sandbox problem

An isolated container is convenient: it starts fast and costs almost nothing. But it has no neighbour to reach, no network to segment, no second machine on which to diagnose a failure. Yet the very skill a learner comes for, deploy, connect, secure, troubleshoot, lives between machines, not inside a single one.

Learning Kubernetes on one container is learning to swim in a bathtub.

A topology per learner

At EduShell, each learner gets not a machine but a topology: a set of connected components, provisioned for them alone.

  • Lightweight containers for workstations and everyday services.
  • Real virtual machines when the exercise touches the kernel, low-level networking or a full operating system.
  • Per-learner Kubernetes clusters, isolated from one another.
  • All wired by isolated networks: several interfaces, separate segments, exactly like production.

Nothing to install, all in the browser, hosted in Europe.

Verification that attests

Handing over an infrastructure isn't enough: you still need to know whether the learner succeeded. Our checks don't ask a multiple-choice question, they inspect the real machine.

bash
kubectl get pods -n production

The check runs against the learner's environment, reads the real state, a running pod, a responding port, a correctly declared resource, and then attests. We don't validate an intention; we validate a result.

What it changes

For the trainer, the whole class is supervised live: they see who's progressing, who's stuck, and can take over a workstation without leaving their dashboard.

For the learner, the exercise finally looks like the job. What they gain isn't a detached set of commands, but the real gesture, in a real system.

In short

A terminal teaches commands. A topology teaches a craft. That's the difference we build, environment after environment, and it's what this blog will be about.


All posts