Hi, I've deployed a single-node kubernetes cluster in our company (Ubuntu 16.04 LTS virtual, cluster installed via kubeadm, using flannel overlay network) and have been very happy about it up until today. Now I've run a system update (and also tried to change --service-node-port-range, but I don't think that's the problem and have reverted it since), rebooted and since then I can't access any cluster IPs either from pods or from the host itself.
These are the packages that have been upgraded: lxc-common:amd64 (2.0.6-0ubuntu1~ubuntu16.04.2, 2.0.7-0ubuntu1~16.04.1) os-prober:amd64 (1.70ubuntu3, 1.70ubuntu3.3) sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3) console-setup-linux:amd64 (1.108ubuntu15.2, 1.108ubuntu15.3) open-vm-tools:amd64 (2:10.0.7-3227872-2ubuntu1, 2:10.0.7-3227872-5ubuntu1~16.04.1) console-setup:amd64 (1.108ubuntu15.2, 1.108ubuntu15.3) libklibc:amd64 (2.0.4-8ubuntu1.16.04.2, 2.0.4-8ubuntu1.16.04.3) lxd:amd64 (2.0.8-0ubuntu1~ubuntu16.04.2, 2.0.9-0ubuntu1~16.04.1) liblxc1:amd64 (2.0.6-0ubuntu1~ubuntu16.04.2, 2.0.7-0ubuntu1~16.04.1) docker-engine:amd64 (1.13.0-0~ubuntu-xenial, 1.13.1-0~ubuntu-xenial) libdrm2:amd64 (2.4.67-1ubuntu0.16.04.2, 2.4.70-1~ubuntu16.04.1) keyboard-configuration:amd64 (1.108ubuntu15.2, 1.108ubuntu15.3) klibc-utils:amd64 (2.0.4-8ubuntu1.16.04.2, 2.0.4-8ubuntu1.16.04.3) lxd-client:amd64 (2.0.8-0ubuntu1~ubuntu16.04.2, 2.0.9-0ubuntu1~16.04.1) base-files:amd64 (9.4ubuntu4.3, 9.4ubuntu4.4) lxcfs:amd64 (2.0.5-0ubuntu1~ubuntu16.04.1, 2.0.6-0ubuntu1~16.04.1) I'm guessing this would be some bridging/iptables problem, but haven't much experience with either (except for some simple ACCEPT/DROP iptables rules) and don't know how to even start debugging the problem. I've also noticed the kube-dns and kube-flannel-ds pods showing Error state for some time, but they became Ready shortly afterwards. I've looked at the log files for the various cluster parts, but found nothing extraordinary (which probably isn't all that surprising, since the components themselves are probably OK, unlike the underlying networking structure). I've also read most of the troubleshooting and FAQ docs sections, but this problem doesn't seem to be covered anywhere. Could someone at least point me to some troubleshooting tips, please? -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
