gdimitropoulos-sotec
commented
4 years ago Same issue hier:
K3s - Server (Master)
iptables v1.8.2 (legacy)
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian
K3s - Agent (Worker)
iptables v1.6.2
ID="poky" NAME="Poky (Yocto Project Reference Distro)" VERSION="2.7.3 (warrior)" VERSION_ID="2.7.3" PRETTY_NAME="Poky (Yocto Project Reference Distro) 2.7.3 (warrior)"
Nodes on Master
NAME | STATUS | ROLES | AGE | VERSION
geopi | Ready | master | 13d | v1.18.4+k3s1
socp2001-00000024 | Ready |
Pods on Master
NAMESPACE | NAME | READY | STATUS | RESTARTS | AGE kube-system | svclb-traefik-kql6t | 0/2 | ContainerCreating | 0 | 59m kube-system | svclb-traefik-j49gj | 2/2 | Running | 16 | 13d kube-system metrics-server-7566d596c8-jntsz | 1/1 | Running | 29 | 13d kube-system | local-path-provisioner-6d59f47c7-vhd8d | 1/1 | Running | 29 | 13d kube-system | coredns-8655855d6-j8c5q | 1/1 | Running | 8 | 13d kube-system | helm-install-traefik-zmg25 | 0/1 | Completed | 1 | 46m kube-system | traefik-758cd5fc85-pnszn | 1/1 Running | 0 | 46m
Describe pod svclb-traefik-kql6t
$ sudo kubectl describe pods svclb-traefik-kql6t -n kube-system
Name: svclb-traefik-kql6t
Namespace: kube-system
Priority: 0
Node: socp2001-00000024/192.168.20.10
Start Time: Thu, 02 Jul 2020 10:29:21 +0200
Labels: app=svclb-traefik
controller-revision-hash=7977679675
pod-template-generation=1
svccontroller.k3s.cattle.io/svcname=traefik
Annotations:
Normal Scheduled
matthiasfeurer
brandond
ruben-sch
ffeldhaus
stale[bot]
Version: k3s version v1.17.2+k3s1 (cdab19b0)
start k3s on master (Ubuntu 18.10): $ curl -sfL https://get.k3s.io | sh -
start k3s on worker (debian): $ sudo k3s agent --server https://myserver:6443 --token ${NODE_TOKEN}
Describe the bug When launching k3s client on a Google coral dev board, node becomes ready but traefik pod is stuck ContainerCreating
To Reproduce 1) start k3s as master (Ubuntu 18.10) 2) start k3s as client (debian - Google coral dev board)
Expected behavior nodes become ready, all pods start.
Actual behavior master node becomes ready with all pods in Running state. client node becomes ready but traefik pod stuck in ContainerCreating state
Additional context Output from client after k3s started - same as when describing the stuck pod:
E0220 00:20:48.531846 15491 pod_workers.go:191] Error syncing pod 195307d4-3ec1-4b57-8e8f-9572173e0fbe ("svclb-traefik-mlvhs_kube-system(195307d4-3ec1-4b57-8e8f-9572173e0fbe)"), skipping: failed to "CreatePodSandbox" for "svclb-traefik-mlvhs_kube-system(195307d4-3ec1-4b57-8e8f-9572173e0fbe)" with CreatePodSandboxError: "CreatePodSandbox for pod \"svclb-traefik-mlvhs_kube-system(195307d4-3ec1-4b57-8e8f-9572173e0fbe)\" failed: rpc error: code = Unknown desc = failed to setup network for sandbox \"fa65e9e2e3c3047b8554313431b1dc651cde6af3e737daf4708b75b65c200c52\": unable to create chain CNI-HOSTPORT-SETMARK: running [/var/lib/rancher/k3s/data/81d6cc7e694228aa5c7660807dc235d0023eba04b407935a202018e9b905f655/bin/iptables -t nat -C CNI-HOSTPORT-SETMARK -m comment --comment CNI portfwd masquerade mark -j MARK --set-xmark 0x2000/0x2000 --wait]: exit status 2: iptables v1.8.3 (legacy): Couldn't find match
comment'\n\nTryiptables -h' or 'iptables --help' for more information.\n"