Upgrading on etcd

Upgrading etcd clusters and applications

Mon, 01 Jan 0001 00:00:00 +0000

This section contains documents specific to upgrading etcd clusters and applications.

Upgrade policy

Before upgrading, note that etcd only supports the following two upgrade cases:

Patch upgrade: Upgrading between patch releases within the same minor version (e.g. 3.7.0 - 3.7.1).
Minor upgrade: Upgrading one minor version at a time (e.g. 3.6 - 3.7). Upgrades that skip a minor version are not supported and will likely fail. Update to the most recent patch version before upgrading to the next minor version.

Upgrading an etcd v3.x cluster

Upgrading from etcd v2.3

Upgrade a v2.3 cluster to v3.0

Upgrade etcd from v3.5 to v3.6

Mon, 01 Jan 0001 00:00:00 +0000

In the general case, upgrading from etcd v3.5 to v3.6 can be a zero-downtime, rolling upgrade:

one by one, stop the etcd v3.5 processes and replace them with etcd v3.6 processes
after running all v3.6 processes, new features in v3.6 are available to the cluster

Before starting an upgrade, read through the rest of this guide to prepare.

Upgrade checklists

Update 3.5

Important

Before upgrading to 3.6, make sure that all of your 3.5 members are updated to 3.5.26 or later. Patch releases 3.5.24 through 3.5.26 fix several potential upgrade blockers.

Upgrade etcd from 3.4 to 3.5

Mon, 01 Jan 0001 00:00:00 +0000

In the general case, upgrading from etcd 3.4 to 3.5 can be a zero-downtime, rolling upgrade:

one by one, stop the etcd v3.4 processes and replace them with etcd v3.5 processes
after running all v3.5 processes, new features in v3.5 are available to the cluster

Before starting an upgrade, read through the rest of this guide to prepare.

Upgrade checklists

Note

When migrating from v2 with no v3 data, etcd server v3.2+ panics when etcd restores from existing snapshots but no v3 ETCD_DATA_DIR/member/snap/db file. This happens when the server had migrated from v2 with no previous v3 data. This also prevents accidental v3 data loss (e.g. db file might have been moved). etcd requires that post v3 migration can only happen with v3 data. Do not upgrade to newer v3 versions until v3.0 server contains v3 data.

Upgrade etcd from 3.3 to 3.4

Mon, 01 Jan 0001 00:00:00 +0000

In the general case, upgrading from etcd 3.3 to 3.4 can be a zero-downtime, rolling upgrade:

one by one, stop the etcd v3.3 processes and replace them with etcd v3.4 processes
after running all v3.4 processes, new features in v3.4 are available to the cluster

Before starting an upgrade, read through the rest of this guide to prepare.

Upgrade checklists

Note

Upgrade etcd from v3.6 to v3.7

Mon, 01 Jan 0001 00:00:00 +0000

In the general case, upgrading from etcd v3.6 to v3.7 can be a zero-downtime, rolling upgrade:

one by one, stop the etcd v3.6 processes and replace them with etcd v3.7 processes
after running all v3.7 processes, new features in v3.7 are available to the cluster

Before starting an upgrade, read through the rest of this guide to prepare.

Upgrade checklists

Update 3.6

Important

Before upgrading to 3.7, make sure that all of your 3.6 members are updated to 3.6.11 or later. Earlier 3.6 patch releases may not be compatible with a rolling upgrade to 3.7.

Upgrade etcd from 3.2 to 3.3

Mon, 01 Jan 0001 00:00:00 +0000

In the general case, upgrading from etcd 3.2 to 3.3 can be a zero-downtime, rolling upgrade:

one by one, stop the etcd v3.2 processes and replace them with etcd v3.3 processes
after running all v3.3 processes, new features in v3.3 are available to the cluster

Before starting an upgrade, read through the rest of this guide to prepare.

Upgrade checklists

Note

Upgrade etcd from 3.1 to 3.2

Mon, 01 Jan 0001 00:00:00 +0000

In the general case, upgrading from etcd 3.1 to 3.2 can be a zero-downtime, rolling upgrade:

one by one, stop the etcd v3.1 processes and replace them with etcd v3.2 processes
after running all v3.2 processes, new features in v3.2 are available to the cluster

Before starting an upgrade, read through the rest of this guide to prepare.

Upgrade checklists

Note

Upgrade etcd from 3.0 to 3.1

Mon, 01 Jan 0001 00:00:00 +0000

In the general case, upgrading from etcd 3.0 to 3.1 can be a zero-downtime, rolling upgrade:

one by one, stop the etcd v3.0 processes and replace them with etcd v3.1 processes
after running all v3.1 processes, new features in v3.1 are available to the cluster

Before starting an upgrade, read through the rest of this guide to prepare.

Upgrade checklists

Note

Upgrade etcd from 2.3 to 3.0

Mon, 01 Jan 0001 00:00:00 +0000

In the general case, upgrading from etcd 2.3 to 3.0 can be a zero-downtime, rolling upgrade:

one by one, stop the etcd v2.3 processes and replace them with etcd v3.0 processes
after running all v3.0 processes, new features in v3.0 are available to the cluster

Before starting an upgrade, read through the rest of this guide to prepare.

Upgrade checklists

Note