202502070003 Migration Plan

With the k3s homelab up and running (and also reproducible), I would like to imagine that it would be useful to create a gameplan on which applications can be migrated over.

Currently, I have introduced a few abstractions via the k8s-libsonnet library (more on my choice to use Grafana Tanka later) to create mostly a basic deployment object and also a persistentVolumeClaim object.

With this in mind, I think it would be relevant to consider the order of priority w.r.t to moving over my applications. I consider that some applications that cannot be migrated over to an externalised, networked storage can consequently live with its sqlite embedded db.

1. Applications can live with a Sqlite storage config
   1. Actual Budget ✅
   2. Uptime Kuma ✅
   3. FlareSolvrr ✅
2. Applications already on an external database
   1. Linkwarden (PG)
   2. Nextcloud (MariaDB)
   3. Paperless (PG)
3. Applications that require a migration from Sqlite to external networked storage
   1. *arr stack + Deluge
   2. JellySeer
   3. Vaultwarden (rebuild with PSQL image) ✅