3 ms·
It's not mentioned in the blog post—is there a document that explains the migration plan for the etcd that ships on the host in CoreOS? Edit: They haven't been
by Perceptes 10y ago
It's not mentioned in the blog post—is there a document that explains the migration plan for the etcd that ships on the host in CoreOS?
Edit: They haven't been published to the docs on the CoreOS website yet, but there are two documents listed under "upgrading and compatibility" at the bottom of https://github.com/coreos/etcd/blob/v3.0.0/Documentation/docs.md https://github.com/coreos/etcd/blob/v3.0.0/Documentation/doc...
- philips 10y agoGreat question. The upgrade path is a rolling upgrade from v2.3.y series to v3.0.0 series. This is how all of the etcd upgrades have worked since the start of v2.x.y. Doc is here: https://github.com/coreos/etcd/blob/master/Documentation/upgrades/upgrade_3_0.md https://github.com/coreos/etcd/blob/master/Documentation/upg...
- Perceptes 10y agoSeems worth noting as well that this only upgrades the version of the cluster. Data populated via the v2 API will not magically be available via the v3 API as they have separate data stores/keyspaces. https://github.com/coreos/etcd/blob/v3.0.0/Documentation/op-guide/v2-migration.md https://github.com/coreos/etcd/blob/v3.0.0/Documentation/op-... talks about how to migrate data that was stored with v2 to v3's data store.