We are using 1.0.0 and want to get to 1.6.0. Is there a recommended upgrade path to get to 1.6.0?
Also is there anything we need to consider when upgrading. I am aware of the obvious things like backups and snapshots, etc. I am thinking more about problems we may encounter.
You could study the upgrade guides:
I think the recommended way is to upgrade to the latest release of the minor version an then go further with the next minor version.
1.0.0 -> 1.1.0 -> 1.1.2 -> 1.2.0 -> 1.2.7 -> 1.3.0… And so on.
It depends on the storage backend. But, in theory, you can go straight from 1.0 to 1.6 but there will be some edges you need to test which will require reading thru all the upgrade notes, as @Wolfsrudel mentioned. However, I wouldn’t do each version in step. Not sure there’s a firm reason to do so.
My rec would be to practice, doc a runbook, run-thru the runbook a few times and make sure it works… Then run your functional tests on the upgraded version. Then destroy and redo it all again, retest. Then, execute the real upgrade.
If you’re planning to move to integrated storage backend, I’d upgrade to 1.4.x, do the migration from whatever-backend to IS, then upgrade Vault to latest.
All the better. I only know it from other software, for example MySQL, which describes the upgrade paths like this. I only took it over 1 to 1.