docs: drop Virtual-Machine.md

It documented the retired KubeVirt workflow (upload a qcow2, create the vm
in k8s-gitops, let Flux create it), which no longer exists. The general
deployment notes live in the README and the per-platform docs
(hosts/k8s/README.md for the microVMs).
This commit is contained in:
Ryan Yin committed 2026-09-21 17:26:38 +08:00
1 parent e939c54d26
commit dbeef8bfaa
2 files changed
+3 -36

No files matched your search

+3 -4
View File
@@ -27,12 +27,11 @@ This repository is home to the Nix code that builds all of my systems:
agenix.
2. **macOS desktops** — nix-darwin + Home Manager, sharing the same `home/` configuration with the
NixOS desktops.
3. **NixOS servers** — VMs running on three physical mini PCs, hosting K3s clusters,
monitoring, and other self-hosted services.
3. **NixOS servers** — three physical mini PCs running the VMs (libvirt and microVMs), the K3s test
cluster and the self-hosted services.
See [./hosts](./hosts) for the host inventory, [./outputs](./outputs) for how the flake outputs are
composed, [./Virtual-Machine.md](./Virtual-Machine.md) for creating & managing VMs, and
[./AGENTS.md](./AGENTS.md) for the repository conventions.
composed, and [./AGENTS.md](./AGENTS.md) for the repository conventions.
## Why NixOS & Flakes?
-32
View File
@@ -1,32 +0,0 @@
## How to create & manage VMs (the retired KubeVirt path)
> [!NOTE] KubeVirt is being retired. aquamarine runs natively on `youko` and the k3s-test
> nodes run as [microVMs](./hosts/k8s/README.md); this document only covers the VMs that
> are left to move (currently the Windows VM).
Use `aquamarine` as an example, first build and upload the virtual machine's qcow2 image to the file
server:
```shell
just upload-vm aquamarine
```
Then create the virtual machine by creating a yaml file at
[ryan4yin/k8s-gitops](https://github.com/ryan4yin/k8s-gitops/tree/main/vms), set the
`spec.dataVolumeTemplates[0].source.http.url` to the uploaded file's URL, and fluxcd will
automatically apply the changes, then a virtual machine named `aquamarine` will be created in the
VM cluster.
Once the virtual machine `aquamarine` is created, we can deploy updates to it with the following
commands:
```shell
just col aquamarine
just col shoryu
# Set a configuration for the next boot instead of switching immediately
just col aquamarine boot
```
If you're not familiar with remote deployment, please read this tutorial first:
[Remote Deployment - NixOS & Flakes Book](https://nixos-and-flakes.thiscute.world/best-practices/remote-deployment)