SQLite versus etcd datastore for a single‑node k3s developer cluster: startup speed vs backup/restore trade‑off
When setting up a repeatable single‑node k3s development environment, the choice of datastore influences both the time to reach a usable cluster and the effort required to restore a known state after a teardown. The embedded SQLite store starts instantly and needs no external service, but creating a consistent backup requires stopping the server or migrating