github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-27 13:37:30 +00:00
Code Issues Projects Releases Wiki Activity

Document k8s.gcr.io/etcd image upgrade/downgrade support

Browse Source
This commit is contained in:
Joe Betz 2018-02-21 16:23:02 -08:00
parent b114a117f8
commit 62ef33744a
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
cluster/images/etcd/README.md
View File

@ -5,6 +5,24 @@ This is a small etcd image used in Kubernetes setups where `etcd` is deployed as
For `amd64`, official `etcd` and `etcdctl` binaries are downloaded from Github to maintain official support. For `amd64`, official `etcd` and `etcdctl` binaries are downloaded from Github to maintain official support.
For other architectures, `etcd` is cross-compiled from source. Arch-specific `busybox` images serve as base images. For other architectures, `etcd` is cross-compiled from source. Arch-specific `busybox` images serve as base images.
### Upgrading and Downgrading
To upgrade to a newer etcd version, or to downgrade to the previous minor
version, always run `/usr/local/bin/migrate-if-needed.sh` before starting the
etcd server.
`migrate-if-needed.sh` writes a `version.txt` file to track the "current" version
of etcd that was used to persist data to disk. A "target" version may also be provided
by the `TARGET_STORAGE` (e.g. "etcd3") and `TARGET_VERSION` (e.g. "3.2.11" )
environment variables. If the persisted version differs from the target version,
`migrate-if-needed.sh` will migrate the data from the current to the target
version.
Upgrades to any target version are supported. The data will be automatically upgraded
in steps to each minor version until the target version is reached.
Downgrades to the previous minor version of the 3.x series and from 3.0 to 2.3.7 are supported.
#### How to release #### How to release
First, run the migration and rollback tests. First, run the migration and rollback tests.