Hey @cerebrate!
Honestly, I think it would be that simple. My kubernetes-based instance has the following PVCs:
~ ❯ k get pvc -n mastodon 16:17:07
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
data-mastodon-elasticsearch-master-0 Bound pvc-3088dbf9-3379-45fc-8cee-57305faa8b00 1Gi RWO do-block-storage 180d
data-mastodon-postgresql-0 Bound pvc-344579d1-9f7c-4599-95ba-765fe45e8952 10Gi RWO do-block-storage 296d
redis-data-mastodon-redis-master-0 Bound pvc-5263bd81-d106-4c02-8215-c073fe1f4028 1Gi RWO do-block-storage 296d
~ ❯
So there’s nothing other than the database and the object storage to think about really, in terms of migration. I do remember reading that the redis data is important, and you’ll either need to migrate it, or wait for it to be rebuilt by a scheduled task (I forget which one…)
Let me know how it goes!
David
(David Young :funkypenguin: (@[email protected]) - FNKY)