Overview

KubeVirt Self-Service Portal for Governed VM Requests

Shepherd gives platform teams a self-service front door for KubeVirt virtual machines without removing the controls needed for regulated, multi-team environments.

Why KubeVirt self-service needs guardrails

KubeVirt makes virtual machines native to Kubernetes, but most organizations still need a controlled operating model around those VMs. A self-service portal should answer who can request a VM, which templates and namespaces are available, who approves the request, and how every change is audited.

Request, approve, deliver

Shepherd models VM work as a governed request flow. Users submit VM lifecycle requests through the portal, approvers review the change, and platform rules decide which clusters, namespaces, templates, and instance sizes are available.

  • Create, modify, start, stop, restart, delete, export, and console entrypoints can be governed.
  • Users get a simpler VM workflow while platform teams keep policy and review points visible.
  • Every request keeps context for later audit and operational review.

A practical KubeVirt UI, not just a thin wrapper

The portal is designed around daily VM operations: request forms, approval queues, RBAC-aware resource visibility, browser console entrypoints, and environment-scoped access. It complements KubeVirt instead of replacing the KubeVirt control plane.

Questions teams ask

Is Shepherd a KubeVirt UI?

Yes. Shepherd includes a web UI for KubeVirt VM lifecycle operations, but it is positioned as a governed self-service portal rather than only a resource viewer.

Does the portal replace KubeVirt?

No. KubeVirt still runs the virtual machines on Kubernetes. Shepherd adds the self-service, approval, RBAC, and audit layer around those VM operations.