Lab Architecture¶

This page describes the lab as it runs today: one KVM host, one libvirt NAT network and three VMs. A single-node k0s cluster runs on two of them, and the third provides DNS and identity.

Overview¶

graph TB
    subgraph host["Host: jarvis (Fedora 44, KVM/libvirt)"]
        tofu[OpenTofu + k0sctl + kubectl]
        subgraph net["net-lab 192.168.10.0/24 (virbr1, NAT, gateway .1)"]
            general01["general01 · 192.168.10.9<br/>BIND9 (lab.riupie.com)<br/>Keycloak + PostgreSQL"]
            master01["master01 · 192.168.10.10<br/>k0s controller"]
            worker01["worker01 · 192.168.10.11<br/>k0s worker"]
            lb["MetalLB pool<br/>192.168.10.100-110"]
        end
    end
    git[(github.com/riupie/gitops-fluxcd)]

    tofu -->|provisions| net
    tofu -->|k0sctl apply| master01
    master01 --- worker01
    worker01 -.->|L2 announce| lb
    worker01 -->|Flux pulls| git
    worker01 -->|External-DNS RFC2136| general01
    lb -->|keycloak.lab.riupie.com| general01

Host¶

The host resolves lab.riupie.com through general01 using a systemd-resolved routing domain on virbr1. See Set Up Dynamic DNS, step 8.

Network¶

Address plan:

Virtual machines¶

All VMs use the Debian 12 genericcloud image. SSH user: cloud.

Services¶

general01¶

Kubernetes (lab-cluster)¶

k0s with Calico (CNI) and kube-proxy in IPVS mode. k0sctl installs only flux-operator; everything else is reconciled by Flux from riupie/gitops-fluxcd (clusters/development):

Minimum host requirements¶

The VMs need 5 vCPUs, 14 GB RAM and about 120 GB of disk in total (qcow2 is thin-provisioned, but plan for the full size).