LAB navigation

Each tab keeps one lane legible: control plane, workload, modern workloads, cloud terminals, or the microservice fabric.

public site on vercel, private execution through LAB lanes
read-only until sign in
Microservices tab

This tab keeps the story centered on VKS: tiny pods, a visible service lane, and just enough operator surface to show how jobs move through the system.

Namespace

lab-wm

Runtime

VKS pods

Pattern

Deployment + Service + ConfigMap

Promise

Visible service fabric

Microservice lane

three pods, one service fabric

lab-wm

lab-lane-api

control surface

VKS pod

Queues demo jobs and exposes the operator HTTP lane.

kubectl apply -f manifests/vks/lab-microservices-lane.yaml -n lab-wm

lab-lane-worker

async worker

VKS pod

Polls the API, simulates work, and emits audit events.

kubectl get deploy,svc,pods -n lab-wm

lab-lane-audit

event trail

VKS pod

Keeps a small visible record so the demo feels alive.

kubectl logs deploy/lab-lane-audit -n lab-wm