4 ms·
> upgrading distributed databases live is always going to be quite non-trivial. I understand that the implementation of live upgrades for a distributed databa
by geertj 8y ago
> upgrading distributed databases live is always going to be quite non-trivial.
I understand that the implementation of live upgrades for a distributed database will be complex but this post is about the user experience. Given enough resources, is there a reason that it can't be a single "upgrade now" command? Or maybe slightly more real-world, a 3 step process like: "stage update" -> "test update" -> "start update".
- piva00 8y agoI agree with you, tooling is still lacking a lot in UX on k8s world.
- philips 8y agoThat is the process: https://github.com/coreos/etcd/blob/master/Documentation/upgrades/upgrade_3_1.md#upgrade-procedure https://github.com/coreos/etcd/blob/master/Documentation/upg... for i in members Replace etcd binary Restart etcd process