Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document upgrade and downgrade steps for etcd 3.2 upgrade #59221

Closed
jpbetz opened this issue Feb 1, 2018 · 4 comments
Closed

Document upgrade and downgrade steps for etcd 3.2 upgrade #59221

jpbetz opened this issue Feb 1, 2018 · 4 comments
Assignees
@jpbetz
Labels
area/platform/gce kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Milestone
v1.10

Comments

@jpbetz
Copy link
Contributor

jpbetz commented Feb 1, 2018

For kubernetes 1.10, we've upgraded the default etcd version to 3.2. As part of this we also must document:

  • Steps to upgrade etcd from 3.1 to 3.2
  • Steps to rollback from 3.2 back to 3.1 if anything goes wrong. The downgrade path will be to use etcdctl save/restore, which requires downtime but can be performed with zero data loss.
@jpbetz jpbetz added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Feb 1, 2018
@jpbetz jpbetz added this to the v1.10 milestone Feb 1, 2018
@jpbetz jpbetz self-assigned this Feb 1, 2018
@jpbetz jpbetz mentioned this issue Feb 1, 2018
Merged
@jberkus
Copy link

jberkus commented Feb 2, 2018

Please add priority and kind labels for this issue. It looks needed for 1.10, but we need to know how to sort it when code slush comes, thanks!

@jpbetz jpbetz added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/documentation Categorizes issue or PR as related to documentation. labels Feb 6, 2018
@jberkus
Copy link

jberkus commented Feb 21, 2018

@jpbetz is there a documentation PR for this issue? Please link, thanks.

@jberkus jberkus mentioned this issue Feb 21, 2018
Closed
@jpbetz jpbetz mentioned this issue Feb 22, 2018
Merged
@jpbetz
Copy link
Contributor Author

jpbetz commented Feb 22, 2018

xref #60173. Since we were able to incorporate the rollback support directly into migrate-if-needed.sh, it turns out that we don't need a whole lot of documentation here.

@jberkus
Copy link

jberkus commented Feb 26, 2018

@jpbetz can you please add status/approved-for-milestone so that this issue can stay in 1.10? Thanks.

k8s-github-robot pushed a commit that referenced this issue Mar 1, 2018
Merge pull request #60173 from jpbetz/migration-downgrade-docs
ded2544 
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

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

Fixes #59221
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jpbetz jpbetz

Labels
area/platform/gce kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Milestone
v1.10
Development

No branches or pull requests
3 participants
@jberkus @jpbetz @k8s-ci-robot