kubeadm upgrade docs #4689

Activity

1. roberthbailey

   assigned

   mhausenblas

   on Aug 8, 2017
2. luxas commented on Aug 8, 2017

   

   luxas

   on Aug 8, 2017

   Member

   More actions

   Sounds good to me to do this proactively! :)
   I'd be happy with having you write a WIP PR for this early on based on some runs with a binary from my fork (I can provide one easily for you)

   The sooner we start to write docs, the better. Often this is left to the last minute, which is a bad habit.

   👍React with 👍1Reacted by Michael Hausenblas
3. mhausenblas commented on Aug 8, 2017

   

   mhausenblas

   on Aug 8, 2017

   Author

   More actions

   Awesome, yes, let's do it. Please advise for a starting point @luxas …
4. mhausenblas

   added 2 commits that reference this issue on Aug 11, 2017

   inits the kubeadm upgrade docs

   ...

   8ade9bf

   adds kubeadm upgrade cmd to ToC

   ...

   c29168c
5. zacharysarah

   added

   Actionable

   P2

   Docs Review: Open Issues

   kind/technical-debt

   Tech Review: Open Issues

   on Aug 14, 2017
6. zacharysarah

   removed

   kind/technical-debt

   on Sep 11, 2017
7. steveperry-53

   added a commit that references this issue on Sep 29, 2017

   Release 1.8 (#5659)

   ...

   799eaf4
8. castrojo commented on Sep 29, 2017

   

   castrojo

   on Sep 29, 2017

   Last edited by castrojo

   Member

   More actions

   The first step has the user curling a kubeadm binary. I asked if just waiting for the kubernetes repo to be updated to 1.8 and running the packaged version would work:

   luxas: Problem statement: an `apt-get upgrade` before pulls down a new kubelet for an old API, which is not supported
   jorge: that sounds like it would actually break
   luxas: Yes
   luxas: hence we need to do CLI only first, upgrade the control plane, and then upgrade the node
   lucas: updating the _kubeadm deb_ would reconfigure the kubelet to become unresponsive as well :disappointed:
   

   Perhaps we should be more explicit in telling the user that they need to get the kubeadm binary out of band first and NOT just do an apt update/dist-upgrade even though kubeadm 1.8 will be sitting in the repo.
9. luxas commented on Oct 2, 2017

   

   luxas

   on Oct 2, 2017

   Member

   More actions

   @castrojo Feel free to improve the wording of the guide :)
10. fejta-bot commented on Jan 6, 2018

    

    fejta-bot

    on Jan 6, 2018

    More actions

    Issues go stale after 90d of inactivity.
    Mark the issue as fresh with /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.

    Prevent issues from auto-closing with an /lifecycle frozen comment.

    If this issue is safe to close now please do so with /close.

    Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
    /lifecycle stale
11. k8s-ci-robot

    added

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.

    on Jan 6, 2018
12. tengqm

    closed this as completedon Jan 7, 2018