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 kubeadm upgrade diff at website #832

Closed
neolit123 opened this issue May 17, 2018 · 3 comments
Closed

document kubeadm upgrade diff at website #832

neolit123 opened this issue May 17, 2018 · 3 comments
Assignees
@neolit123
Labels
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/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.11

Comments

@neolit123
Copy link
Member

Some users want to see the changes kubeadm woulda apply before actually running kubeadm upgrade apply. This shows the changes that will be made to the static pod manifests before applying them. This is a narrower case than kubeadm upgrade apply --dry-run, which specifically focuses on the static pod manifests.

adds the `kubeadm upgrade diff` command to show how static pod manifests will be changed by an upgrade.

PR:
kubernetes/kubernetes#63930

/assign
@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label May 17, 2018
@neolit123
Copy link
Member Author

neolit123 commented May 17, 2018 •
edited
Loading

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 17, 2018
@neolit123
Copy link
Member Author

/area UX

@neolit123 neolit123 added this to the v1.11 milestone May 18, 2018
@neolit123 neolit123 mentioned this issue May 18, 2018
Merged
@neolit123 neolit123 added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label May 18, 2018
@neolit123
Copy link
Member Author

Fixed by kubernetes/website#8617

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

@neolit123 neolit123

Labels
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/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.11
Development

No branches or pull requests
2 participants
@neolit123 @k8s-ci-robot