Skip to content
New issue

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

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

Already on GitHub? # to your account

Create a kubeadm upgrade node config command #848

Closed
luxas opened this issue May 22, 2018 · 1 comment · Fixed by kubernetes/kubernetes#64624
Closed

Create a kubeadm upgrade node config command #848

luxas opened this issue May 22, 2018 · 1 comment · Fixed by kubernetes/kubernetes#64624
Assignees
Labels
area/releasing area/upgrades kind/feature Categorizes issue or PR as related to a new feature. 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

Comments

@luxas
Copy link
Member

luxas commented May 22, 2018

This command will fetch the latest kubelet ConfigMap with configuration from the cluster and write it to disk (/var/lib/kubelet/config.yaml), as well as the kubelet runtime flags file (/var/lib/kubelet/kubeadm-flags.env).

For more information see: #822 and kubernetes/kubernetes#63887

@luxas luxas added this to the v1.11 milestone May 22, 2018
@luxas luxas added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/releasing area/upgrades kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. labels May 22, 2018
@luxas luxas self-assigned this May 22, 2018
@luxas
Copy link
Member Author

luxas commented Jun 12, 2018

This was fixed by #848

@luxas luxas closed this as completed Jun 12, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
area/releasing area/upgrades kind/feature Categorizes issue or PR as related to a new feature. 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
Development

Successfully merging a pull request may close this issue.

1 participant