Skip to content

Features overview

What you can do in VirtFoundry after install and first login.

VirtFoundry is a multi-tenant IaaS control plane on Kubernetes: tenants get isolated namespaces, VMs (KubeVirt), disks, VPCs/networks (Multus), security groups, IAM, and a CloudStack-like UI/API.

Capability map

  • Tenancy

    Isolated tenants, root impersonation, delete (non-default).

    Read

  • Auth & IAM

    Users, roles, permissions, API keys (vfd_live_...).

    Read

  • Service offerings

    CPU/memory catalog; shared vs dedicated CPU.

    Read

  • Images & templates

    Container disks and ISO (CDI) images.

    Read

  • Virtual machines

    Deploy, start/stop, attach volumes, logs, snapshots.

    Read

  • Console & SSH

    noVNC console, SSH keys, expose SSH.

    Read

  • Volumes & snapshots

    Volumes; VM snapshots vs CSI volume snapshots.

    Read

  • VPCs & networks

    VPCs, private nets, CIDR planners, public profile.

    Read

  • Security groups

    Security groups become NetworkPolicy.

    Read

  • Kubernetes clusters (VKS)

    Managed Kubernetes: Kamaji control plane, VM workers.

    Read

  • API quick reference

    JWT / API keys, X-Tenant-ID, route map.

    Read

Domain model

Tenant
  ├── VPC ── Network (Multus NAD)
  │         └── Security group (NetworkPolicy)
  ├── Volume ── Volume snapshot (CSI)
  └── VM ── NICs ── Network
       ├── Service offering (CPU/mem)
       ├── VM template (image)
       └── VM snapshot (KubeVirt)

Rule: the tenant is the isolation unit. VMs and volumes live in the tenant namespace; each VPC has its own namespace; NICs attach via Multus.

UI map

Sidebar Paths
Dashboard /dashboard
Compute /vms, /templates, /ssh-keys, /vm-snapshots, /console
Storage /volumes, /snapshots
Network /vpcs, /networks, /networks/public, /security-groups
Platform /iam, /offerings (root), /tenants (root)

Next