karolflont
9a58393192
Ubuntu 16.04.5 LTS apt-mark unhold kubeadm && apt-get update && apt-get install -y kubeadm=1.14.x-00 && apt-mark hold kubeadm gives the below error The following packages have unmet dependencies: kubelet : Depends: kubernetes-cni (= 0.6.0) but 0.7.5-00 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Unholding the kubelet with kubeadm fixes the problem.
380 lines
17 KiB
Markdown
380 lines
17 KiB
Markdown
---
|
|
reviewers:
|
|
- sig-cluster-lifecycle
|
|
title: Upgrading kubeadm clusters from v1.13 to v1.14
|
|
content_template: templates/task
|
|
---
|
|
|
|
{{% capture overview %}}
|
|
|
|
This page explains how to upgrade a Kubernetes cluster created with kubeadm from version 1.13.x to version 1.14.x,
|
|
and from version 1.14.x to 1.14.y (where `y > x`).
|
|
|
|
The upgrade workflow at high level is the following:
|
|
|
|
1. Upgrade the primary control plane node.
|
|
1. Upgrade additional control plane nodes.
|
|
1. Upgrade worker nodes.
|
|
|
|
{{< note >}}
|
|
With the release of Kubernetes v1.14, the kubeadm instructions for upgrading both HA and single control plane clusters
|
|
are merged into a single document.
|
|
{{</ note >}}
|
|
|
|
{{% /capture %}}
|
|
|
|
{{% capture prerequisites %}}
|
|
|
|
- You need to have a kubeadm Kubernetes cluster running version 1.13.0 or later.
|
|
- [Swap must be disabled](https://serverfault.com/questions/684771/best-way-to-disable-swap-in-linux).
|
|
- The cluster should use a static control plane and etcd pods.
|
|
- Make sure you read the [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.14.md) carefully.
|
|
- Make sure to back up any important components, such as app-level state stored in a database.
|
|
`kubeadm upgrade` does not touch your workloads, only components internal to Kubernetes, but backups are always a best practice.
|
|
|
|
### Additional information
|
|
|
|
- All containers are restarted after upgrade, because the container spec hash value is changed.
|
|
- You only can upgrade from one MINOR version to the next MINOR version,
|
|
or between PATCH versions of the same MINOR. That is, you cannot skip MINOR versions when you upgrade.
|
|
For example, you can upgrade from 1.y to 1.y+1, but not from 1.y to 1.y+2.
|
|
|
|
{{% /capture %}}
|
|
|
|
{{% capture steps %}}
|
|
|
|
## Determine which version to upgrade to
|
|
|
|
1. Find the latest stable 1.14 version:
|
|
|
|
{{< tabs name="k8s_install_versions" >}}
|
|
{{% tab name="Ubuntu, Debian or HypriotOS" %}}
|
|
apt update
|
|
apt-cache policy kubeadm
|
|
# find the latest 1.14 version in the list
|
|
# it should look like 1.14.x-00, where x is the latest patch
|
|
{{% /tab %}}
|
|
{{% tab name="CentOS, RHEL or Fedora" %}}
|
|
yum list --showduplicates kubeadm --disableexcludes=kubernetes
|
|
# find the latest 1.14 version in the list
|
|
# it should look like 1.14.x-0, where x is the latest patch
|
|
{{% /tab %}}
|
|
{{< /tabs >}}
|
|
|
|
## Upgrade the first control plane node
|
|
|
|
1. On your first control plane node, upgrade kubeadm:
|
|
|
|
{{< tabs name="k8s_install_kubeadm_first_cp" >}}
|
|
{{% tab name="Ubuntu, Debian or HypriotOS" %}}
|
|
# replace x in 1.14.x-00 with the latest patch version
|
|
apt-mark unhold kubeadm kubelet && \
|
|
apt-get update && apt-get install -y kubeadm=1.14.x-00 && \
|
|
apt-mark hold kubeadm
|
|
{{% /tab %}}
|
|
{{% tab name="CentOS, RHEL or Fedora" %}}
|
|
# replace x in 1.14.x-0 with the latest patch version
|
|
yum install -y kubeadm-1.14.x-0 --disableexcludes=kubernetes
|
|
{{% /tab %}}
|
|
{{< /tabs >}}
|
|
|
|
1. Verify that the download works and has the expected version:
|
|
|
|
```shell
|
|
kubeadm version
|
|
```
|
|
|
|
1. On the control plane node, run:
|
|
|
|
```shell
|
|
sudo kubeadm upgrade plan
|
|
```
|
|
|
|
You should see output similar to this:
|
|
|
|
```shell
|
|
[preflight] Running pre-flight checks.
|
|
[upgrade] Making sure the cluster is healthy:
|
|
[upgrade/config] Making sure the configuration is correct:
|
|
[upgrade/config] Reading configuration from the cluster...
|
|
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
|
|
[upgrade] Fetching available versions to upgrade to
|
|
[upgrade/versions] Cluster version: v1.13.3
|
|
[upgrade/versions] kubeadm version: v1.14.0
|
|
|
|
Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
|
|
COMPONENT CURRENT AVAILABLE
|
|
Kubelet 2 x v1.13.3 v1.14.0
|
|
|
|
Upgrade to the latest version in the v1.13 series:
|
|
|
|
COMPONENT CURRENT AVAILABLE
|
|
API Server v1.13.3 v1.14.0
|
|
Controller Manager v1.13.3 v1.14.0
|
|
Scheduler v1.13.3 v1.14.0
|
|
Kube Proxy v1.13.3 v1.14.0
|
|
CoreDNS 1.2.6 1.3.1
|
|
Etcd 3.2.24 3.3.10
|
|
|
|
You can now apply the upgrade by executing the following command:
|
|
|
|
kubeadm upgrade apply v1.14.0
|
|
|
|
_____________________________________________________________________
|
|
```
|
|
|
|
This command checks that your cluster can be upgraded, and fetches the versions you can upgrade to.
|
|
|
|
1. Choose a version to upgrade to, and run the appropriate command. For example:
|
|
|
|
```shell
|
|
sudo kubeadm upgrade apply v1.14.x
|
|
```
|
|
|
|
- Replace `x` with the patch version you picked for this ugprade.
|
|
|
|
You should see output similar to this:
|
|
|
|
```shell
|
|
[preflight] Running pre-flight checks.
|
|
[upgrade] Making sure the cluster is healthy:
|
|
[upgrade/config] Making sure the configuration is correct:
|
|
[upgrade/config] Reading configuration from the cluster...
|
|
[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
|
|
[upgrade/version] You have chosen to change the cluster version to "v1.14.0"
|
|
[upgrade/versions] Cluster version: v1.13.3
|
|
[upgrade/versions] kubeadm version: v1.14.0
|
|
[upgrade/confirm] Are you sure you want to proceed with the upgrade? [y/N]: y
|
|
[upgrade/prepull] Will prepull images for components [kube-apiserver kube-controller-manager kube-scheduler etcd]
|
|
[upgrade/prepull] Prepulling image for component etcd.
|
|
[upgrade/prepull] Prepulling image for component kube-scheduler.
|
|
[upgrade/prepull] Prepulling image for component kube-apiserver.
|
|
[upgrade/prepull] Prepulling image for component kube-controller-manager.
|
|
[apiclient] Found 0 Pods for label selector k8s-app=upgrade-prepull-etcd
|
|
[apiclient] Found 0 Pods for label selector k8s-app=upgrade-prepull-kube-scheduler
|
|
[apiclient] Found 0 Pods for label selector k8s-app=upgrade-prepull-kube-controller-manager
|
|
[apiclient] Found 0 Pods for label selector k8s-app=upgrade-prepull-kube-apiserver
|
|
[apiclient] Found 1 Pods for label selector k8s-app=upgrade-prepull-etcd
|
|
[apiclient] Found 1 Pods for label selector k8s-app=upgrade-prepull-kube-controller-manager
|
|
[apiclient] Found 1 Pods for label selector k8s-app=upgrade-prepull-kube-scheduler
|
|
[apiclient] Found 1 Pods for label selector k8s-app=upgrade-prepull-kube-apiserver
|
|
[upgrade/prepull] Prepulled image for component etcd.
|
|
[upgrade/prepull] Prepulled image for component kube-apiserver.
|
|
[upgrade/prepull] Prepulled image for component kube-scheduler.
|
|
[upgrade/prepull] Prepulled image for component kube-controller-manager.
|
|
[upgrade/prepull] Successfully prepulled the images for all the control plane components
|
|
[upgrade/apply] Upgrading your Static Pod-hosted control plane to version "v1.14.0"...
|
|
Static pod: kube-apiserver-myhost hash: 6436b0d8ee0136c9d9752971dda40400
|
|
Static pod: kube-controller-manager-myhost hash: 8ee730c1a5607a87f35abb2183bf03f2
|
|
Static pod: kube-scheduler-myhost hash: 4b52d75cab61380f07c0c5a69fb371d4
|
|
[upgrade/etcd] Upgrading to TLS for etcd
|
|
Static pod: etcd-myhost hash: 877025e7dd7adae8a04ee20ca4ecb239
|
|
[upgrade/staticpods] Moved new manifest to "/etc/kubernetes/manifests/etcd.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests-2019-03-14-20-52-44/etcd.yaml"
|
|
[upgrade/staticpods] Waiting for the kubelet to restart the component
|
|
[upgrade/staticpods] This might take a minute or longer depending on the component/version gap (timeout 5m0s)
|
|
Static pod: etcd-myhost hash: 877025e7dd7adae8a04ee20ca4ecb239
|
|
Static pod: etcd-myhost hash: 877025e7dd7adae8a04ee20ca4ecb239
|
|
Static pod: etcd-myhost hash: 64a28f011070816f4beb07a9c96d73b6
|
|
[apiclient] Found 1 Pods for label selector component=etcd
|
|
[upgrade/staticpods] Component "etcd" upgraded successfully!
|
|
[upgrade/etcd] Waiting for etcd to become available
|
|
[upgrade/staticpods] Writing new Static Pod manifests to "/etc/kubernetes/tmp/kubeadm-upgraded-manifests043818770"
|
|
[upgrade/staticpods] Moved new manifest to "/etc/kubernetes/manifests/kube-apiserver.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests-2019-03-14-20-52-44/kube-apiserver.yaml"
|
|
[upgrade/staticpods] Waiting for the kubelet to restart the component
|
|
[upgrade/staticpods] This might take a minute or longer depending on the component/version gap (timeout 5m0s)
|
|
Static pod: kube-apiserver-myhost hash: 6436b0d8ee0136c9d9752971dda40400
|
|
Static pod: kube-apiserver-myhost hash: 6436b0d8ee0136c9d9752971dda40400
|
|
Static pod: kube-apiserver-myhost hash: 6436b0d8ee0136c9d9752971dda40400
|
|
Static pod: kube-apiserver-myhost hash: b8a6533e241a8c6dab84d32bb708b8a1
|
|
[apiclient] Found 1 Pods for label selector component=kube-apiserver
|
|
[upgrade/staticpods] Component "kube-apiserver" upgraded successfully!
|
|
[upgrade/staticpods] Moved new manifest to "/etc/kubernetes/manifests/kube-controller-manager.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests-2019-03-14-20-52-44/kube-controller-manager.yaml"
|
|
[upgrade/staticpods] Waiting for the kubelet to restart the component
|
|
[upgrade/staticpods] This might take a minute or longer depending on the component/version gap (timeout 5m0s)
|
|
Static pod: kube-controller-manager-myhost hash: 8ee730c1a5607a87f35abb2183bf03f2
|
|
Static pod: kube-controller-manager-myhost hash: 6f77d441d2488efd9fc2d9a9987ad30b
|
|
[apiclient] Found 1 Pods for label selector component=kube-controller-manager
|
|
[upgrade/staticpods] Component "kube-controller-manager" upgraded successfully!
|
|
[upgrade/staticpods] Moved new manifest to "/etc/kubernetes/manifests/kube-scheduler.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests-2019-03-14-20-52-44/kube-scheduler.yaml"
|
|
[upgrade/staticpods] Waiting for the kubelet to restart the component
|
|
[upgrade/staticpods] This might take a minute or longer depending on the component/version gap (timeout 5m0s)
|
|
Static pod: kube-scheduler-myhost hash: 4b52d75cab61380f07c0c5a69fb371d4
|
|
Static pod: kube-scheduler-myhost hash: a24773c92bb69c3748fcce5e540b7574
|
|
[apiclient] Found 1 Pods for label selector component=kube-scheduler
|
|
[upgrade/staticpods] Component "kube-scheduler" upgraded successfully!
|
|
[upload-config] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
|
|
[kubelet] Creating a ConfigMap "kubelet-config-1.14" in namespace kube-system with the configuration for the kubelets in the cluster
|
|
[kubelet-start] Downloading configuration for the kubelet from the "kubelet-config-1.14" ConfigMap in the kube-system namespace
|
|
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
|
|
[bootstrap-token] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
|
|
[bootstrap-token] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
|
|
[bootstrap-token] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
|
|
[addons] Applied essential addon: CoreDNS
|
|
[addons] Applied essential addon: kube-proxy
|
|
|
|
[upgrade/successful] SUCCESS! Your cluster was upgraded to "v1.14.0". Enjoy!
|
|
|
|
[upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so.
|
|
```
|
|
|
|
1. Manually upgrade your CNI provider plugin.
|
|
|
|
Your Container Network Interface (CNI) provider may have its own upgrade instructions to follow.
|
|
Check the [addons](/docs/concepts/cluster-administration/addons/) page to
|
|
find your CNI provider and see whether additional upgrade steps are required.
|
|
|
|
1. Upgrade the kubelet and kubectl on the control plane node:
|
|
|
|
{{< tabs name="k8s_install_kubelet" >}}
|
|
{{% tab name="Ubuntu, Debian or HypriotOS" %}}
|
|
# replace x in 1.14.x-00 with the latest patch version
|
|
apt-mark unhold kubelet kubectl && \
|
|
apt-get update && apt-get install -y kubelet=1.14.x-00 kubectl=1.14.x-00 && \
|
|
apt-mark hold kubelet kubectl
|
|
{{% /tab %}}
|
|
{{% tab name="CentOS, RHEL or Fedora" %}}
|
|
# replace x in 1.14.x-0 with the latest patch version
|
|
yum install -y kubelet-1.14.x-0 kubectl-1.14.x-0 --disableexcludes=kubernetes
|
|
{{% /tab %}}
|
|
{{< /tabs >}}
|
|
|
|
1. Restart the kubelet
|
|
|
|
```shell
|
|
sudo systemctl restart kubelet
|
|
```
|
|
|
|
## Upgrade additional control plane nodes
|
|
|
|
1. Same as the first control plane node but use:
|
|
|
|
```
|
|
sudo kubeadm upgrade node experimental-control-plane
|
|
```
|
|
|
|
instead of:
|
|
|
|
```
|
|
sudo kubeadm upgrade apply
|
|
```
|
|
|
|
Also `sudo kubeadm upgrade plan` is not needed.
|
|
|
|
## Upgrade worker nodes
|
|
|
|
The upgrade procedure on worker nodes should be executed one node at a time or few nodes at a time,
|
|
without compromising the minimum required capacity for running your workloads.
|
|
|
|
### Upgrade kubeadm
|
|
|
|
1. Upgrade kubeadm on all worker nodes:
|
|
|
|
{{< tabs name="k8s_install_kubeadm_worker_nodes" >}}
|
|
{{% tab name="Ubuntu, Debian or HypriotOS" %}}
|
|
# replace x in 1.14.x-00 with the latest patch version
|
|
apt-mark unhold kubeadm kubelet && \
|
|
apt-get update && apt-get install -y kubeadm=1.14.x-00 && \
|
|
apt-mark hold kubeadm
|
|
{{% /tab %}}
|
|
{{% tab name="CentOS, RHEL or Fedora" %}}
|
|
# replace x in 1.14.x-0 with the latest patch version
|
|
yum install -y kubeadm-1.14.x-0 --disableexcludes=kubernetes
|
|
{{% /tab %}}
|
|
{{< /tabs >}}
|
|
|
|
### Cordon the node
|
|
|
|
1. Prepare the node for maintenance by marking it unschedulable and evicting the workloads. Run:
|
|
|
|
```shell
|
|
kubectl drain $NODE --ignore-daemonsets
|
|
```
|
|
|
|
You should see output similar to this:
|
|
|
|
```shell
|
|
node/ip-172-31-85-18 cordoned
|
|
WARNING: ignoring DaemonSet-managed Pods: kube-system/kube-proxy-dj7d7, kube-system/weave-net-z65qx
|
|
node/ip-172-31-85-18 drained
|
|
```
|
|
|
|
### Upgrade the kubelet config
|
|
|
|
1. Upgrade the kubelet config:
|
|
|
|
```shell
|
|
sudo kubeadm upgrade node config --kubelet-version v1.14.x
|
|
```
|
|
|
|
Replace `x` with the patch version you picked for this ugprade.
|
|
|
|
|
|
### Upgrade kubelet and kubectl
|
|
|
|
1. Upgrade the Kubernetes package version by running the Linux package manager for your distribution:
|
|
|
|
{{< tabs name="k8s_kubelet_and_kubectl" >}}
|
|
{{% tab name="Ubuntu, Debian or HypriotOS" %}}
|
|
# replace x in 1.14.x-00 with the latest patch version
|
|
apt-mark unhold kubelet kubectl && \
|
|
apt-get update && apt-get install -y kubelet=1.14.x-00 kubectl=1.14.x-00 && \
|
|
apt-mark hold kubelet kubectl
|
|
{{% /tab %}}
|
|
{{% tab name="CentOS, RHEL or Fedora" %}}
|
|
# replace x in 1.14.x-0 with the latest patch version
|
|
yum install -y kubelet-1.14.x-0 kubectl-1.14.x-0 --disableexcludes=kubernetes
|
|
{{% /tab %}}
|
|
{{< /tabs >}}
|
|
|
|
1. Restart the kubelet
|
|
|
|
```shell
|
|
sudo systemctl restart kubelet
|
|
```
|
|
|
|
### Uncordon the node
|
|
|
|
1. Bring the node back online by marking it schedulable:
|
|
|
|
```shell
|
|
kubectl uncordon $NODE
|
|
```
|
|
|
|
## Verify the status of the cluster
|
|
|
|
After the kubelet is upgraded on all nodes verify that all nodes are available again by running the following command from anywhere kubectl can access the cluster:
|
|
|
|
```shell
|
|
kubectl get nodes
|
|
```
|
|
|
|
The `STATUS` column should show `Ready` for all your nodes, and the version number should be updated.
|
|
|
|
{{% /capture %}}
|
|
|
|
## Recovering from a failure state
|
|
|
|
If `kubeadm upgrade` fails and does not roll back, for example because of an unexpected shutdown during execution, you can run `kubeadm upgrade` again.
|
|
This command is idempotent and eventually makes sure that the actual state is the desired state you declare.
|
|
|
|
To recover from a bad state, you can also run `kubeadm upgrade --force` without changing the version that your cluster is running.
|
|
|
|
## How it works
|
|
|
|
`kubeadm upgrade apply` does the following:
|
|
|
|
- Checks that your cluster is in an upgradeable state:
|
|
- The API server is reachable
|
|
- All nodes are in the `Ready` state
|
|
- The control plane is healthy
|
|
- Enforces the version skew policies.
|
|
- Makes sure the control plane images are available or available to pull to the machine.
|
|
- Upgrades the control plane components or rollbacks if any of them fails to come up.
|
|
- Applies the new `kube-dns` and `kube-proxy` manifests and makes sure that all necessary RBAC rules are created.
|
|
- Creates new certificate and key files of the API server and backs up old files if they're about to expire in 180 days.
|
|
|
|
`kubeadm upgrade node experimental-control-plane` does the following on additional control plane nodes:
|
|
- Fetches the kubeadm `ClusterConfiguration` from the cluster.
|
|
- Optionally backups the kube-apiserver certificate.
|
|
- Upgrades the static Pod manifests for the control plane components.
|