1. Create a Sandbox
Create a Sandbox from an image, TTL, and subnet:--name, the CLI generates a concrete Sandbox name before creating
the resource.
Output similar to:
--name when you want to choose the resource name:
15m, 2h, or 24h.
2. Request an isolation class
Use--isolation-class when the target subnet allows the requested isolation
class:
container, secure-container, and microvm. Use
secure-container for untrusted code: the Sandbox’s system calls are served by
an application kernel instead of the host kernel. Use microvm when the
Sandbox needs its own guest kernel; it is in preview and requires provider
nodes on hosts with KVM. The value maps to the Sandbox pod template and must
be admitted by the target subnet. For the guarantee each class gives, see
Workload isolation.
3. Inspect Sandboxes
List Sandboxes in the current namespace:4. Apply a Sandbox manifest
Use a manifest when the Sandbox definition should be repeatable. Manifest workflows requiremetadata.name.

