Explore the KubeVirt Shepherd demo without a cluster
Use the public browser demo to inspect the interface before planning a self-hosted installation. No account or Kubernetes credentials are needed.
Enter as a developer
Open the demo, choose Developer and enter. Browse the Systems, Services and Virtual Machines views to see how a workload is organized.
Inspect a VM request
In Virtual Machines, open Request VM. The guided and full-form modes collect the service, template, instance size, namespace and business reason. The demo includes a demo-test namespace and simulated catalog choices.
Compare roles and request records
Open My Requests, then use the demo role control to compare the developer and approver views. Reset data in that tab when you want to return to the seeded examples.
This walkthrough checks the browser experience. It does not validate server authorization, VM scheduling, authentication providers or a live VNC connection. Demo state is isolated to the current browser tab.
Start with ownership
Systems group business resources, with Services beneath them. Find the intended service before inspecting its VMs or requesting another one. A scoped product list is not an inventory of everything in Kubernetes.
Read tickets and VM state differently
A ticket describes a requested change and its workflow outcome. The VM view describes the managed resource. Successful submission is not a running VM, and an old approval is not evidence of current health.
Understand the operational view
The administrator observability view supports operational investigation. A self-hosted installation can use documented metrics and tracing. Synthetic demo charts do not demonstrate your cluster performance or a configured monitoring backend.
Walk through the task
Choose a demo role
Locate a System, its Service and the VM list. Note which navigation and actions are available for that role.
Inspect one VM in context
Review ownership and resource details before taking an action. Use the owning service as the starting point for a request.
Follow a request across views
Submit a request, inspect its ticket and change demo roles to examine review work. Return to the VM view after the decision.
Read the workflow handoffRepeat, then plan a live check
Reset the demo to repeat the tour. For real provider errors or monitoring signals, connect a test cluster and configure the documented observability inputs.
Read the observability baseline
Requirements and limits
- Demo resources, execution results and monitoring data are simulated.
- VNC/serial sessions and real admission checks require a connected installation.
- Demo role switching is an exploration control, not the authentication design for your own deployment.
Documentation and implementation
- Project overview
Current scope, architecture and Alpha status.
- Request handoff
Responsibilities represented by the UI.
- Observability scope
Implemented signals, optional assets and deferred work.
- Run a connected installation
Requirements for live provider and console validation.
Common questions
Does the demo connect to my clusters?
No. It uses simulated data. Use a self-hosted installation with explicit cluster connectivity for a live evaluation.
Does an empty list mean no VMs exist?
Not necessarily. Check the service, filters and account access. Resource visibility is scoped; it is not a global Kubernetes inventory.