Hey 👋 we kinda missed the latest
# spicedbd
dguhr84
07/04/2023, 7:46 AMHey 👋 we .. kinda missed the latest spiceDB updates, so a maybe silly question: Is it ok/safe to update from 1.20.0 to 1.22.2 directly, or should we do an intermediate update first?
dguhr84
07/04/2023, 8:01 AMI guess
Copy code
We highly recommend updating sequentially through SpiceDB minor versions (e.g. 1.0.0 -> 1.1.0) to avoid headaches. Jumping many versions at once might cause you to miss instructions for a particular release that could lead to downtimev
vroldanbet
07/04/2023, 8:31 AMright, this is what the operator handles automatically for you. It has an update graph baked into it, and knows the sequence of steps versions and migrations to run.
It'd be advisable to check the release notes of each version to understand if there are migrations involved, if there are multi-phase migrations involved, or if there are breaking changes to the dispatch API which would make it incompatible to cluster together pods from different versions.
d
dguhr84
07/04/2023, 8:37 AMThanks for the answer. Currently it'd be no problem to have a downtime, and yes, the operator would be awesome, and I'll poke internal constraints again for that one 🙂
dguhr84
07/04/2023, 8:38 AMsafest is update to 1.21.0, then to 1.22.2 I guess, with downtime, right?
dguhr84
07/04/2023, 8:38 AM(I'd avoid 1.22.0 bc of the warning in the release notes)
v
vroldanbet
07/04/2023, 9:50 AMwhat database are you running?
vroldanbet
07/04/2023, 9:51 AMthe only migration that I'm aware of is Spanner in 1.22.0
vroldanbet
07/04/2023, 9:51 AMand yes, 1.21 -> 1.22.2 is the recommended route. It will cause some errors as dispatch APIs are incompatible, but should recover by itself
d
dguhr84
07/04/2023, 9:52 AMpostgres
dguhr84
07/04/2023, 9:54 AMso we don't need to use the migrate head command then, right?
v
vroldanbet
07/04/2023, 10:34 AMyeah, according to the update graph there are no migrations involved for PG: https://github.com/authzed/spicedb-operator/blob/main/validated-update-graph.yaml#L169-L177
vroldanbet
07/04/2023, 10:34 AMand you could also technically move directly to 1.22.2
vroldanbet
07/04/2023, 10:35 AMyou can see in the edges section the possible update paths https://github.com/authzed/spicedb-operator/blob/main/validated-update-graph.yaml#L493-L497
vroldanbet
07/04/2023, 10:36 AMI think 1.20 was removed from the graph as it had some perf regression, if I'm not mistaken. @ecordell?
e
ecordell
07/05/2023, 1:33 PMyeah, 1.20 just wasn't added to the graph. no point in running it once 1.21 became available.
looks like we're all set now though!
d
dguhr84
07/06/2023, 7:56 AM@ecordell we are all set, ty! 🙂 Out of curiosity, as I didn't monitor the developments lately: The spiceDB operator is not currently available to use namespace scoped, right? We have some constraints on a multi-tenant platform to deploy it cluster scoped(permissions, security issues like access to secrets, ...) and being able to run it ns-scoped would be great.
2 Views