Set up k3s on this VM by following the exe.dev recipe at https://exe.dev/deploy/k3s.md from top to bottom. The recipe's example VM name is my-k3s. This VM's name is the output of `hostname`: use it wherever the recipe writes my-k3s. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - k3s v1.37.2+k3s1 running as a systemd service, with pod and service networks that don't clash with the VM's own. - kubectl and Helm working for `exedev` without sudo. - Traefik answering on port 8000, with a sample app at the VM's private URL that shows your exe.dev email. - PersistentVolumeClaims backed by the VM's disk through the local-path provisioner. - Nightly backups of the cluster state, server token and volumes, with the first one checked. Read the whole recipe, including the closed details, and follow "Install by hand" from top to bottom: the k3s config, the Traefik config, k3s itself, Helm, the sample app, and the backup timer. Use the pinned versions as written. The walkthrough sections are for the owner afterwards: don't install podinfo or other charts, add nodes, set up Tailscale, copy the VM, or run the Restore, Update or Uninstall instructions during setup. Leave the VM private and do not reboot. Check `kubectl get nodes` shows one Ready node named k3s, every pod in kube-system is Running or Completed, and `curl localhost:8000` returns the whoami output. Finish with the VM's private URL and the two commands that give the owner kubectl on their own computer. Finish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them): ssh my-k3s.exe.xyz cat /etc/rancher/k3s/k3s.yaml | sed 's/:6443/:16443/' > my-k3s.kubeconfig # then KUBECONFIG=my-k3s.kubeconfig ssh -N -L 16443:localhost:6443 my-k3s.exe.xyz