Schedule¶
120 minutes total. Times are from the start of the workshop.
Two versions
Below is the schedule as submitted. The revised schedule in the plan is what we intend to actually run — it adds buffer and turns Lab 3 into a demo. The reasons are in the Premise review.
As submitted¶
| Time | Duration | Block |
|---|---|---|
| 00:00 | 15 min | 1 · What is Agentic Cloud Ops? |
| 00:15 | 15 min | 2 · Local cluster bootstrap |
| 00:30 | 30 min | 3 · Lab 1 — Your first agent |
| 01:00 | 35 min | 4 · Lab 2 — Security and hardening |
| 01:35 | 15 min | 5 · Lab 3 — Chaos and recovery |
| 01:50 | 10 min | 6 · Q&A and wrap-up |
No formal break
Two hours without a break is tight. Stretch whenever you like — the labs are self-contained and each has a checkpoint you can jump to if you fall behind.
For facilitators¶
- Verify
make cluster-upon both macOS (arm64) and Linux well before the conference. - Lab 1 depends on a deliberately planted
ImagePullBackOff. Confirm it triggers. - Lab 2 is the longest and most important block — protect its time. Cut Lab 3 instead.
- Have an offline plan: pre-pulled images and a tarball of the agent tooling.
- Run
make cluster-downat the end, together with the participants.