- Open source
- KubeVirt
- ArgoCD
Point. Click. Pull request.
A web console for KubeVirt that edits git, not the cluster. VMs, networks and firewalls, point-and-click. Every config change is a pull request that ArgoCD applies.
The UI stages. The forge gates. ArgoCD applies.
The path of every config change, from a click to the cluster.
-
Stage
Edit in the UI. dotvirt writes the manifest, not the cluster.
-
Propose
One pull request per project, with the exact diff.
-
Merge
Review and approve in your forge, under your rules.
-
Sync
ArgoCD applies git. Live state reads back in seconds.
A console your virtualization team already knows.
One live inventory of projects, namespaces and VMs, filtered by your own RBAC.
Power, console and live migration, next to where the VM stands between git and the cluster.
Stage edits, read the manifest diff, open one pull request. History and undo come with git.
Every firewall tier in one view. Trace a flow and see the rule that decided.
Gateways, segments and VLANs as a topology, each one declared in git.
A thin lens that owns nothing.
-
Acts as you
Every request runs under your own cluster token. Cluster RBAC is the only permission model.
-
Git is the record
Each change is a commit with an author and a diff. Review it, revert it, audit it.
-
ArgoCD applies
dotvirt never writes config to the cluster. Merging the pull request does.
- VNC console
- Live migration
- Snapshots and clones
- VM templates
- Host balancing
- Drift detection
- Adopt running VMs
- Flow tracing
- Single sign-on
- Dark mode
One resource installs it.
- Install the operator, from OperatorHub on OpenShift or the OLM catalog in the repo.
- Create one
Dotvirtresource. The operator provisions the console, its RBAC, the ArgoCD wiring and an optional Forgejo.
Needs KubeVirt and ArgoCD. Runs on OpenShift and vanilla Kubernetes.
apiVersion: dotvirt.io/v1alpha1
kind: Dotvirt
metadata:
name: dotvirt
namespace: dotvirt
spec:
forge:
managed: true # or point at your own forge
ingress:
type: auto # Route or Ingress