We've never included upgrade instructions for installations using containers in our release notes. Should we? What would we even write? I'm working on the release notes for 6.4 (#10853) and I'm struck by how a classic installation is assumed. See the 6.3 upgrade instructions, for example.
First of all, much of the undeploy/deploy shennaningans don't apply to us.
Same goes for copying domaindirs and such stuff
The other parts like executing some curl commands against your DB, load metadata schemas etc is more or less the same
A notable difference is the likelyhood of not doing this from what looks like localhost to DV, so you need to add the unblock-key stuff to admin endpoints
Are we telling people to have a DB backup done before upgrading?
We could include how to do that with Docker/K8s. On the other hand, we don't include this for a classic installation, do we?
It might be nice to explain, maybe some place else, not in the release notes, how you can test an update with containers and a snapshot of your production database before actually deploying it to production
Yes, great ideas.
Last updated: Oct 30 2025 at 05:14 UTC