Downgrading on etcd

Downgrading etcd clusters and applications

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

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

Downgrading an etcd v3.x cluster

Downgrade etcd from 3.5 to 3.4

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

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

one by one, stop the etcd 3.5 processes and replace them with etcd 3.4 processes
after starting any 3.4 processes, new features in 3.5 are not longer available to the cluster

Before starting a downgrade, read through the rest of this guide to prepare.

Downgrade checklists

content/en/docs/v3.5/op-guide/authentication/rbac.md

NOTE: If your cluster enables auth, rolling downgrade from 3.5 isn’t supported because 3.5 changes a format of WAL entries related to auth. You can follow the authentification instructions to disable auth, and delete all users first.

Downgrade etcd from v3.6 to v3.5

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

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

one by one, stop the etcd v3.6 processes and replace them with etcd v3.5 processes
after enabling the downgrade, new features in v3.6 are no longer available to the cluster

Before starting a downgrade, read through the rest of this guide to prepare.

Downgrade checklists

Highlighted breaking changes from v3.6 to v3.5:

Difference in flags

If you are using any of the following flags in your v3.6 configurations, make sure to remove, rename, or change the default value when downgrading to v3.5.