Try Kubernetes

Get Started

Ready to get your hands dirty? Build a simple Kubernetes cluster that runs "Hello World" for Node.js.

Documentation

Learn how to use Kubernetes with the use of walkthroughs, samples, and reference documentation. You can even help contribute to the docs!

Community

If you need help, you can connect with other Kubernetes users and the Kubernetes authors, attend community events, and watch video presentations from around the web.

Blog

Read the latest news for Kubernetes and the containers space in general, and get technical how-tos hot off the presses.

Interested in hacking on the core Kubernetes code base?

View On Github

Explore the community

Tasks

Step-by-step instructions for performing operations with Kubernetes.

Documentation for Kubernetes v1.9 is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.

Edit This Page

Upgrading kubeadm clusters from 1.6 to 1.7

This guide is for upgrading kubeadm clusters from version 1.6.x to 1.7.x. Upgrades are not supported for clusters lower than 1.6, which is when kubeadm became Beta.

WARNING: These instructions will overwrite all of the resources managed by kubeadm (static pod manifest files, service accounts and RBAC rules in the kube-system namespace, etc.), so any customizations you may have made to these resources after cluster setup will need to be reapplied after the upgrade. The upgrade will not disturb other static pod manifest files or objects outside the kube-system namespace.

Before you begin
On the master
On each node

Before you begin

You need to have a Kubernetes cluster running version 1.6.x.

On the master

Upgrade system packages.

Upgrade your OS packages for kubectl, kubeadm, kubelet, and kubernetes-cni.

a. On Debian, this can be accomplished with:
```
sudo apt-get update
sudo apt-get upgrade
```
b. On CentOS/Fedora, you would instead run:
```
sudo yum update
```
Restart kubelet.
```
systemctl restart kubelet
```
Delete the kube-proxy DaemonSet.

Although most components are automatically upgraded by the next step, kube-proxy currently needs to be manually deleted so it can be recreated at the correct version:
```
sudo KUBECONFIG=/etc/kubernetes/admin.conf kubectl delete daemonset kube-proxy -n kube-system
```
Perform kubeadm upgrade.

WARNING: All parameters you passed to the first kubeadm init when you bootstrapped your cluster MUST be specified here in the upgrade-kubeadm init-command. This is a limitation we plan to address in v1.8.
```
sudo kubeadm init --skip-preflight-checks --kubernetes-version <DESIRED_VERSION>
```
For instance, if you want to upgrade to 1.7.0, you would run:
```
sudo kubeadm init --skip-preflight-checks --kubernetes-version v1.7.0
```
Upgrade CNI provider.

Your CNI provider might have its own upgrade instructions to follow now. Check the addons page to find your CNI provider and see if there are additional upgrade steps necessary.

On each node

Upgrade system packages.

Upgrade your OS packages for kubectl, kubeadm, kubelet, and kubernetes-cni.

a. On Debian, this can be accomplished with:
```
sudo apt-get update
sudo apt-get upgrade
```
b. On CentOS/Fedora, you would instead run:
```
sudo yum update
```
Restart kubelet.
```
systemctl restart kubelet
```

Create an Issue Edit this Page