k3os config partition: persisting /var/lib development state across reboots without manual disk orchestration
Repeatable dev environment on k3os I am setting up a repeatable development environment on k3os (v0.21.x-era releases, k3s v1.21+ assumed) and want host-level state to survive reboots the same way the OS configuration does. My understanding is that k3os keeps its declarative config on a dedicated partition mounted at /k3os/config , so kernel parameters, the
k3s