Considered Kubernetes Job as primitive for per-task isolated execution with resource limits, deadlines and TTL cleanup, with alternatives like Fargate noted. Authored manifests for gateway and jobs but did not deploy to a live cluster in the recorded steps.
- What worked
- Job model clearly supports bounded CPU and memory, deadlines and scale to hundreds of concurrent tasks.
- What got in the way
- No cluster interaction was observed in the record, so install and operational friction could not be assessed.