mirror of
https://github.com/ryan4yin/nix-config.git
synced 2026-11-15 04:52:04 +01:00
Ryan Yin
b9c5d3e5c9
hosts/k8s/README.md: how the microVMs keep state, the tap/br0 naming, how to move a KubeVirt VM over in place, and the refreshed TODOs. Also note the migration in Virtual-Machine.md and flag the volume images in AGENTS.md.
33 lines
1.3 KiB
Markdown
33 lines
1.3 KiB
Markdown
## How to create & managage KubeVirt's Virtual Machine from this flake?
|
|
|
|
> [!NOTE] KubeVirt is being retired. aquamarine runs natively on `kubevirt-youko` and the k3s-test
|
|
> nodes run as [microVMs](./hosts/k8s/README.md); this document only covers the KubeVirt 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
|
|
KubeVirt cluster.
|
|
|
|
Once the virtual machine `aquamarine` is created, we can deploy updates to it with the following
|
|
commands:
|
|
|
|
```shell
|
|
just col aquamarine
|
|
just col kubevirt-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)
|