Spot Capacity Orchestrator · View 18 of 32 · 5 · Runtime
The order that matters
- Mark unschedulable, stop routing new work, then signal the workload, in that order, so drain never races new arrivals. The taint is applied before eviction even when the API is slow, falling back to the local path at 800 ms.
- Verification is an observation, not a return code: no pods and no job steps left on the node. A node still running work at T+118 s is recorded as an overrun, a distinct event that flags the contract as one the workload cannot honour.
Numbers
- Notice to drain signal 1.4 s here against a 2 s p99 budget. Final checkpoint 1.4 GB in 31 s against 45 s p99 for 2 GB. Overruns budgeted at ≤ 0.5% of reclamations.
What is never done
- The drain is never extended past the provider's deadline. The deadline belongs to a guaranteed tenant who was promised capacity; the platform's job is to finish inside it or lose the work knowingly and count it.