From a calendar invite to three clouds — and back to nothing.
Book a workshop or a challenge. Attendee accounts and cloud environments build themselves at the start time, and clean themselves up when it ends. Here is the whole path.
Schedule
An organizer books a workshop or challenge on a calendar — date, size and clouds. Nothing is provisioned or billed until it starts.
Provision
About two hours ahead of the start it builds itself: a Google account per attendee, a Harness org, and the requested cloud environments via Terraform — ready when the room opens.
Run
Each attendee signs in to their own ready-made environment and works through the labs. Time can be extended a day at a time.
Clean up
When the timer runs out, every account, project and org is torn down on a schedule — nothing is left running by accident.
A run's lifecycle, build-up to teardown
scheduled
On the calendar, waiting. Nothing exists yet — no accounts, no cloud spend — until about two hours before the start, when the scheduler picks it up.
provisioning
A Google Workspace org-unit is created, then one attendee account per seat, each with a generated temporary password to hand out.
Harness org
every eventRegardless of cloud, a Harness organization is created with one project per attendee — each attendee admins their own and can view the rest.
applying
Terraform builds every requested cloud. In challenge mode each competitor gets their own project, account or resource group instead of a shared one.
Terraform, one state per cloudGoogle CloudGKE- Ephemeral project
- Billing linked, APIs enabled
- GKE cluster
- Attendees granted Editor
AWSEKS- Member account
- An IAM user each
- EKS cluster
- PowerUser access
AzureAKS- Resource group
- An Entra user each
- AKS cluster
- Contributor access
A workshop can also request no cloud — attendees share a long-lived sandbox project, so there is nothing throwaway to build or destroy.
ready
environments liveOutputs are published and the expiry timer is set. The organizer hands out credentials and the room is open.
in session
Attendees work in their own environments. The organizer can extend the deadline a day at a time from the event's page.
destroying
In reverse, on a timer: clouds first (they hold the access), then the Harness projects and org, then the attendee accounts, then the org-unit.
destroyed
Everything is gone. Nothing left running, nothing left billing.
Any step can end in failed — the run stops and stays on the calendar, flagged, so nothing is half-built in the dark. It’s retried or reaped from there.
Ready to run one?
Pick a date, a size and the clouds. The orchestrator takes it from there.