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

Implement easy upgrades with one command: kubeadm upgrade #14

Closed
mikedanese opened this issue Nov 22, 2016 · 7 comments · Fixed by kubernetes/kubernetes#48899 or kubernetes/kubernetes#50872
Assignees
Labels
area/upgrades kind/tracking-issue priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@mikedanese
Copy link
Member

From @danielschonfeld on October 28, 2016 10:49

Wanted to make a wish. Being a long time kubernetes user and having stitched clusters by hand, I am convinced kubeadm is the best thing that happened to kubernetes in terms of mass adoption. I think it would be nice if we could do version upgrades with kubeadm. I imagine it wouldn't be too hard needing only to update the versions in the manifests and download a new version of kubelet?

Is there something else I'm missing? Could this become a reality?

Copied from original issue: kubernetes/kubernetes#35779

@luxas luxas added area/upgrades kind/enhancement kind/tracking-issue priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Nov 25, 2016
@luxas luxas added this to the v1.6 milestone Nov 25, 2016
@luxas luxas removed this from the v1.6 milestone Feb 9, 2017
@ekozan
Copy link

ekozan commented Mar 31, 2017

any news of this one ? ✌️

@luxas
Copy link
Member

luxas commented May 29, 2017

@ekozan Yes, see: kubernetes/enhancements#296

@luxas luxas added this to the v1.8 milestone May 29, 2017
@jamiehannaford
Copy link
Contributor

I imagine when self-hosting becomes more stable (hopefully completed by v1.8), this will just be a matter of documentation. I'll add it to our v1.8 goals.

@luxas luxas self-assigned this Jun 17, 2017
@luxas
Copy link
Member

luxas commented Jun 17, 2017

Yes, this is definitely a v1.8 goal

@luxas
Copy link
Member

luxas commented Jun 29, 2017

This is happening for v1.8, if you're interested, take a look at this google doc that I just updated with new info:
https://docs.google.com/document/d/1PRrC2tvB-p7sotIA5rnHy5WAOGdJJOIXPPv23hUFGrY/edit

@luxas luxas changed the title kubeadm upgrade proposal Implement easy upgrades with one command: kubeadm upgrade Aug 18, 2017
@luxas
Copy link
Member

luxas commented Aug 18, 2017

The implementation PR is here: kubernetes/kubernetes#48899

@luxas
Copy link
Member

luxas commented Aug 25, 2017

Not quite yet fixed, one of two PRs for this has merged

@luxas luxas reopened this Aug 25, 2017
k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this issue Sep 3, 2017
Automatic merge from submit-queue

Implement the `kubeadm upgrade` command

**What this PR does / why we need it**:

Implements the kubeadm upgrades proposal: https://docs.google.com/document/d/1PRrC2tvB-p7sotIA5rnHy5WAOGdJJOIXPPv23hUFGrY/edit#

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #

fixes: kubernetes/kubeadm#14

**Special notes for your reviewer**:

I'm gonna split out changes not directly related to the upgrade procedure into separate PRs as dependencies as we go.
**Now ready for review. Please look at `cmd/kubeadm/app/phases/upgrade` first and give feedback on that. The rest kind of follows.**

**Release note**:

```release-note
Implemented `kubeadm upgrade plan` for checking whether you can upgrade your cluster to a newer version
Implemented `kubeadm upgrade apply` for upgrading your cluster from one version to an other
```

cc @fabriziopandini @kubernetes/sig-cluster-lifecycle-pr-reviews @craigtracey @mattmoyer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/upgrades kind/tracking-issue priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
6 participants