Shulou(Shulou.com)05/31 Report--

This article mainly explains "what are the problems after the upgrade of Kubernetes 1.16.x". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn what are the problems after the upgrade of Kubernetes 1.16.x.

1. Major changes

In addition to the mirrored versions of several major apiserver/controller/scheduler services that become 1.16.3, others include:

Etcd uses 3.3.15-0 (not the latest 4.x series yet).

CoreDNS uses 1.6.2 (1.15.x or 1.3.1, which varies a lot), which can cause startup failures.

2. Docker support

The Ubuntu system automatically upgrades Docker-CE to 19.3.4, but uses kubectl get node-owide to get node information discovery, which is always in Not Ready state.

Check status: kubectl describe node/podc01, found that CNI failed.

Downgrade it to 19.3.2.

Methods:

Check the available version: sudo apt list docker-ce-a

Install the established version: sudo apt install docker-ce=xxxxxx

Update the / etc/docker/daemon.json

3 、 CoreDNS

CoreDNS uses 1.6.2 (1.15.x or 1.3.1, which varies a lot), which can cause startup failures.

See https://github.com/Azure/aks-engine/pull/1493

The main reason is that if the Docker Image is upgraded directly, the configuration parameters are not upgraded synchronously.

But the old parameters are not applicable to the new version, which is more tragic.

You can only expect to release a new parameter or upgrade tool, or later CoreDNS will encapsulate the cross-version configuration parameters in the image.

At present, there is no better solution to this problem, waiting for the awesome people of the CoreDNS community to act.

4 、 Dashboard

Dashboard 1.x is only supported to 1.15, upgrade image to 1.10.1 is not allowed, and it is no longer maintained or updated.

Kubernetes 1.16.x can only use Dashboard 2.x.

But this is still under development, and the latest one is Beta5.

There are several big changes in Dashboard 2.x:

This is convenient for Chinese users, you can directly pull down the system.

The default installation template namespace is kubernetes-dashboard, not kube-system.

The position of the Docker image has changed, it has been extracted from gcr, and it has become kubernetesui/dashboard:v2.0.0-beta5.

Installation instructions after installing Dashboard 2.x, log in to the system, the information will not be displayed.

5 、 JupyterHub

The original JupuyterHub for K8s runs well, but after the upgrade, Server will not start up.

Go in and check the information:

Supermap@podc01:~$ kubectl get pod-n jupyter-owideNAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATEShub-75d575499b-6d76n 1 podc03 kubectl logs hub-75d575499b-6d76n 1 Running 0 19m 10.244.0.15 podc02 proxy-589655677b-qcfrm 1 Running 0 19m 10.244.1.140 podc03 kubectl logs hub-75d575499b-6d76n-n jupyter

Both pod and svc of hub and proxy are OK.

Further check hub's log:

Kubectl logs pod/hub-75d575499b-6d76n-n jupyter

Get the following error message that JupyterHub started Notebook Server is an error during the execution of the script:

E 2019-10-28 07 hub/user/supermap/ 46 JupyterHub log:158 58.604 JupyterHub log:158] 500 GET / 167.95ms (supermap@10.244.7.0) 1028.54ms [I 2019-10-28 07 7 hub/user/supermap/ 47 JupyterHub log:158 18.636 JupyterHub log:158] 302 GET / hub/spawn-> / user/supermap/ (supermap@10.244.7.0) 167.95ms [I 2019-10-28 7 hub/user/supermap/ 4718.672 JupyterHub log:158] 302 GET / user/supermap/-> / hub / user/supermap/ (@ 10.244.7.0) 1.02ms [E 2019-10-28 07 purge 47 JupyterHub user:477 19.404 JupyterHub user:477] Unhandled error starting supermap's server:'

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.