1.14 upgrade
# spicedb
j
I've got a SpiceDB instance at 1.13 in a k8s cluster and am looking at the 1.14 migrations on Postgres. (Yes I'm behind!) I'm not currently using the operator, but thought about installing it to navigate through the 1.14 upgrade+migrations. We've used Flyway for previous migrations but this looks a little trickier. Can the k8s operator migrate to 1.14 on postgres without downtime? Could the operator adopt an existing SpiceDB instance seamlessly? Are there flyway or other user-contributed migrations available if not?
e
The operator will upgrade through the steps without downtime, the cluster will remain available the whole time. Instead of adopting existing pods (which I think should be possible but we dont have the steps written down anywhere) it’s probably easier to spin up a new cluster with the same config pointed to the same backing DB, and then shift traffic over when you’re ready
No flyway migrations as far as I know, can it handle migrations of binaries (and cli flags) or is it sql only?
j
Thank you so much for the help!
For flyway, we had been manually migrating the database schema between each version and separately upgrading the container. During a release, the database migrator would run first and honestly spicedb would just fail until the migrator completed. Not the ideal way to upgrade I suppose..
8 Views