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.

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

include more details about the kubeadm upgrade backup process #1694

Closed
neolit123 opened this issue Jul 29, 2019 · 4 comments · Fixed by kubernetes/website#18424
Closed

include more details about the kubeadm upgrade backup process #1694

neolit123 opened this issue Jul 29, 2019 · 4 comments · Fixed by kubernetes/website#18424
Assignees
Labels
area/upgrades area/UX kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone

Comments

@neolit123
Copy link
Member

neolit123 commented Jul 29, 2019

during upgrade if the process fails on static pods, kubeadm writes a folder called /etc/kubernetes/backup.

currently we do not:

  • document how this folder works. WIP
  • have test coverage when kubeadm falls back to a manifest in the backup folder. EDIT: we have some unit tests for this.

xref: #1617 (comment)

@neolit123 neolit123 added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/backlog Higher priority than priority/awaiting-more-evidence. area/upgrades area/test area/UX kind/documentation Categorizes issue or PR as related to documentation. labels Jul 29, 2019
@neolit123 neolit123 added this to the v1.16 milestone Jul 29, 2019
@Klaven
Copy link

Klaven commented Aug 14, 2019

I will document this and start working on the test coverage.

@neolit123 neolit123 removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Aug 14, 2019
@neolit123 neolit123 modified the milestones: v1.16, v1.17 Sep 23, 2019
@neolit123
Copy link
Member Author

adding help-wanted to see if someone wants to take this one.
/help

@k8s-ci-robot
Copy link
Contributor

@neolit123:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

adding help-wanted to see if someone wants to take this one.
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Nov 9, 2019
@neolit123 neolit123 modified the milestones: v1.17, v1.18 Nov 13, 2019
@neolit123 neolit123 self-assigned this Jan 1, 2020
@neolit123 neolit123 added lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. and removed help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. area/test labels Jan 1, 2020
@neolit123 neolit123 changed the title document and test the kubeadm upgrade backup process include more details about the kubeadm upgrade backup process Jan 2, 2020
@neolit123
Copy link
Member Author

a PR for this is here:
https://github.com/kubernetes/website/pull/18424/files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/upgrades area/UX kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants