Healthcare batch platform
The operations owner at fictional North Harbor Scheduling requests a nightly availability export. Deliver an isolated namespace, an account without automatic token mounting, persistent output, a CronJob and declared traffic/resource budgets. Use an original fixture command and retain every earlier definition.
A healthcare scheduling team needs a batch workspace with persistent output and limited privileges. The data is fictional and contains no patient information. You'll create a namespace and workload identity, request storage, define the scheduled job, then record traffic and resource constraints. Carry each resource forward; later definitions must reference the identities created earlier. The final deliverable is a coherent local resource set, not an assertion that a production controller has run the schedule. The project also makes two boundaries explicit: service account identity doesn't grant permissions by itself, and a declared network policy needs a compatible plugin for enforcement in a real cluster.
kubectl create namespace schedules-east
A worked first action on this original project fixture.