Skip to content

Commit

Permalink
WIP upgrade guide for kubeadm clusters.
Browse files Browse the repository at this point in the history
  • Loading branch information
pipejakob committed Jun 6, 2017
1 parent 9f2ecee commit 403f61b
Show file tree
Hide file tree
Showing 2 changed files with 57 additions and 0 deletions.
1 change: 1 addition & 0 deletions _data/tasks.yml
Original file line number Diff line number Diff line change
Expand Up @@ -110,6 +110,7 @@ toc:
- docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods.md
- docs/tasks/administer-cluster/cluster-management.md
- docs/tasks/administer-cluster/upgrade-1-6.md
- docs/tasks/administer-cluster/kubeadm-upgrade-1-7.md
- docs/tasks/administer-cluster/namespaces.md
- docs/tasks/administer-cluster/namespaces-walkthrough.md
- docs/tasks/administer-cluster/dns-horizontal-autoscaling.md
Expand Down
56 changes: 56 additions & 0 deletions docs/tasks/administer-cluster/kubeadm-upgrade-1-7.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
---
assignees:
- pipejakob
title: Upgrading kubeadm clusters to 1.7
redirect_from:
- "/docs/admin/kubeadm-upgrade-1-7/"
- "/docs/admin/kubeadm-upgrade-1-7.html"
---

* TOC
{:toc}

This guide is for upgrading kubeadm clusters from version 1.6.x to 1.7.x, or
other 1.6.x releases. Upgrades are not supported before the 1.6.0 release (when
kubeadm became Beta).

It is a work-in-progress (not intended for merging yet) and targeted at other
developers hoping to exercise the instructions to test the upgrade process.

1. Back up `/etc/kubernetes`.

2. Upgrade system packages.

Upgrade kubectl, kubeadm, kubelet, and kubernetes-cni via OS packages

a. On Debian, this would be:

sudo apt-get update
sudo apt-get install kubelet kubeadm kubelet kubernetes-cni

b. On CentOS/Fedora, this would be:

sudo yum update
sudo yum install kubelet kubeadm kubelet kubernetes-cni

TODO: For testing purposes, build candidate .debs/.rpms and include alternate
instructions for installing them.

3. Perform kubeadm upgrade.

kubeadm init --skip-preflight-checks --kubernetes-version <DESIRED_VERSION>`

At release time, this would be:

kubeadm init --skip-preflight-checks --kubernetes-version v1.7.0

For pre-release testing, this would be:

kubeadm init --skip-preflight-checks --kubernetes-version v1.7.0-beta.0

4. Upgrade CNI provider.

Your CNI provider might have its own upgrade instructions to follow now.

TODO: Rollback instructions in case anything goes wrong (using the backed up
files from step 1).

0 comments on commit 403f61b

Please sign in to comment.