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.

Sign up for GitHub

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

Jump to bottom

Amend 1.16 kubeadm upgrade guide #19995

Merged
merged 1 commit into from
Apr 7, 2020
Merged

Amend 1.16 kubeadm upgrade guide #19995

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -237,6 +237,24 @@ The upgrade workflow at high level is the following:

This step is not required on additional control plane nodes if the CNI provider runs as a DaemonSet.

One common issue you may encounter if you are using Flannel network is
that after the upgrade, the cluster nodes remain in `NotReady` state.
If you do `kubectl get nodes -o yaml`, you may see following lines in the
output:

```
message:docker: network plugin is not ready: cni config uninitialized
```

In this case, you will need to update the `/etc/cni/net.d/10-flannel.conflist`
file to include the `cniVersion` line, as shown below:

```
"name": "cbr0",
"cniVersion": "0.2.0",
"plugins": [ ...
```

Copy link
Member

@neolit123 neolit123 Mar 31, 2020 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tengqm i think we should add this to https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/troubleshooting-kubeadm/ instead.

and link to the troubleshooting guide from the upgrade guide.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is specific to 1.15.x -> 1.16.y upgrade, right?
moving the content to troubleshooting is a good idea.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think its only for 1.16 yes, but also something to note is that the kubeadm team is finding it difficult to support flannel at this point. too many issues compared to e.g. WeaveNet or Calico.

1. Uncordon the control plane node

```shell
Expand Down