kvm2: integration test, sample Proxy, providers-config entries and Makefile target

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

config/samples/kustomization.yaml

@@ -5,5 +5,6 @@ resources:
 - proxy_kubernetes.yaml
 - proxy_gcp.yaml
 - proxy_kvm.yaml
+- proxy_kvm2.yaml
 - proxy_external.yaml
 # +kubebuilder:scaffold:manifestskustomizesamples

config/samples/providers-config.yaml

@@ -55,3 +55,34 @@ providers:
           bridge: br0                 # to a LAN with DHCP; the VM's IP comes from there
           # socket: /var/run/libvirt/libvirt-sock
           # pool: default
+  # kvm2 takes the same block shape as kvm: an entry ports by changing type
+  # to kvm2 and the block name to kvm2. kvm2 does not adopt domains made by
+  # kvm, so delete those Proxies first. See docs/kvm2-provider.md.
+  # - name: kvm2-home
+  #   type: kvm2
+  #   kvm2:
+  #     sshKeyFile: /etc/proxy-operator/kvm/id_ed25519
+  #     knownHostsFile: /etc/proxy-operator/kvm/known_hosts
+  #     # insecureIgnoreHostKey: true
+  #     # diskSizeGb: 10
+  #     # installGuestAgent: false
+  #     # vendorData: |
+  #     #   #cloud-config
+  #     #   ...
+  #     images:
+  #       debian-13:
+  #         url: https://cloud.debian.org/images/cloud/trixie/latest/debian-13-generic-amd64.qcow2
+  #         # sha256: "<64 hex>"
+  #         # firmware: uefi
+  #       ubuntu-24.04:
+  #         url: https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img
+  #     machineTypes:
+  #       small:  {vcpus: 1, memoryMiB: 1024}
+  #       medium: {vcpus: 2, memoryMiB: 2048}
+  #     hosts:
+  #       - name: beelink
+  #         address: beelink:22
+  #         user: novakj
+  #         bridge: br0
+  #         # socket: /var/run/libvirt/libvirt-sock
+  #         # pool: default

config/samples/proxy_kvm2.yaml

@@ -0,0 +1,44 @@
+# A Managed proxy backed by a libvirt/KVM hypervisor through the kvm2
+# provider: the operator boots a stock Debian cloud image as a VM on the
+# named host, with a NIC on the host's bridge (IP from the LAN's DHCP), and
+# installs Squid via cloud-init. Requires a providers-config entry named
+# "kvm2-home" (see providers-config.yaml) and the kvm-ssh Secret, which the
+# kvm and kvm2 providers share (docs/kvm2-provider.md).
+#
+# placement.zone is the host name from kvm2.hosts (optional when only one
+# host is configured); machineType and image are keys in the provider's
+# machineTypes and images maps. The first Proxy for an image on a host
+# waits for the image download; later ones reuse the cached copy.
+apiVersion: crawl.example.com/v1alpha1
+kind: Proxy
+metadata:
+  name: proxy-kvm2-sample
+spec:
+  mode: Managed
+  provider: kvm2-home
+  placement:
+    zone: beelink
+    machineType: small
+    image: debian-13
+  port: 3128
+  cloudInit:
+    inline: |
+      #cloud-config
+      packages:
+        - squid
+      write_files:
+        - path: /etc/squid/conf.d/proxy-operator.conf
+          content: |
+            http_port 3128
+            http_access allow all
+            via off
+            forwarded_for off
+      runcmd:
+        - systemctl restart squid
+      # Optional: log in with `ssh debian@<ip>` (the Debian image's default
+      # user) to look around; `virsh console <name>` on the host works too.
+      # ssh_authorized_keys:
+      #   - ssh-ed25519 AAAA... you@laptop
+  attributes:
+    geo: home
+    purpose: crawl