Prepare the owning service
You need access to the System and Service, permission to create VMs and an allowed environment. Available namespaces, templates and sizes depend on your account. If a choice is missing, ask the resource owner to check access and catalog configuration.
Submit workload intent
The create contract requires a service, template, instance size, namespace and business reason. Optional resource targets remain subject to validation. The requester does not submit a cluster ID; the platform generates the VM name. The namespace cannot be changed after submission.
Verify delivery separately
Reviewers confirm eligible cluster and storage placement. After a decision, inspect execution and the resulting VM state. Approval does not prove that storage, admission or guest startup has succeeded.
Walk through the task
Confirm the System and Service
Choose the service that should own the VM. Resolve missing membership with its owner instead of creating a duplicate service.
Read the two access layersChoose the request inputs
Select an available template, instance size and registered namespace. Review placement guidance, then add a reason that explains the workload.
Inspect VMCreateRequest and request contextSubmit and retain the ticket
Check the namespace carefully before submitting once. Follow the ticket while the reviewer checks placement; a hint is not a reservation of capacity.
Read requester and reviewer responsibilitiesCheck the resulting VM
Inspect the ticket outcome and VM state. Keep any execution error for the platform operator. In the browser demo, this transition uses simulated data.
Requirements and limits
- The public demo does not provision a real VM or reserve cluster resources.
- A connected installation needs working Kubernetes/KubeVirt access, catalogs and suitable namespace permissions.
- An approved request can still fail during execution; a decision and live VM health are different checks.
Documentation and implementation
- Request and placement responsibilities
Accepted requester/reviewer boundary.
- Current create API
See /vms/request-context, /vms/request and VMCreateRequest.
- Access and membership model
Platform capabilities, inherited resource access and environments.
- Deployment requirements
Infrastructure and configuration behind the form.
Common questions
Why is there no cluster selector?
The create payload deliberately omits cluster_id. You request a workload in a namespace; the reviewer selects an eligible deployment cluster.
Can the reviewer correct my namespace?
The submitted namespace is immutable. Resolve the incorrect request with the reviewer and submit the right context rather than treating placement as a namespace change.