This message was deleted Rancher Users #k3s

Join Slack

This message was deleted.

# k3s

adamant-kite-43734

12/09/2022, 10:36 AM

This message was deleted.

chilly-telephone-51989

12/11/2022, 6:11 AM

so far Ithink that dns service isn't responding to the requests. When I run the busy box and try to lookup

nslookup gateway

I get this only after deleting the coredns pod and re-spawn. before that I wasn't able to get anything except timeout errors

Copy code

nslookup gateway
Server:		10.43.0.10
Address:	10.43.0.10:53

Name:	gateway.xplorie.svc.cluster.local
Address: 10.43.156.140

** server can't find gateway.svc.cluster.local: NXDOMAIN

** server can't find gateway.svc.cluster.local: NXDOMAIN


** server can't find gateway.cluster.local: NXDOMAIN

** server can't find gateway.cluster.local: NXDOMAIN

** server can't find gateway.us-east-2.compute.internal: NXDOMAIN

** server can't find gateway.us-east-2.compute.internal: NXDOMAIN

i had seen this error before and then the reason was that traefik wasn't able to find the gateway.

chilly-telephone-51989

12/11/2022, 6:21 AM

Copy code

ks get pods -o wide
NAME                                      READY   STATUS      RESTARTS      AGE    IP            NODE              NOMINATED NODE   READINESS GATES
helm-install-traefik-crd-jh2nn            0/1     Completed   0             87d    10.42.0.3     ip-172-31-46-55   <none>           <none>
helm-install-traefik-rzcq4                0/1     Completed   2             87d    10.42.0.2     ip-172-31-46-55   <none>           <none>
svclb-traefik-12c86e56-9728x              2/2     Running     2 (87d ago)   87d    10.42.1.3     ip-172-31-34-0    <none>           <none>
svclb-traefik-12c86e56-k8w7g              2/2     Running     8 (86d ago)   87d    10.42.2.19    ip-172-31-41-97   <none>           <none>
svclb-traefik-12c86e56-kz9fc              2/2     Running     4 (44h ago)   87d    10.42.0.15    ip-172-31-46-55   <none>           <none>
local-path-provisioner-7b7dc8d6f5-w7f68   1/1     Running     3 (44h ago)   87d    10.42.0.16    ip-172-31-46-55   <none>           <none>
metrics-server-668d979685-9gxfk           1/1     Running     3 (44h ago)   87d    10.42.0.19    ip-172-31-46-55   <none>           <none>
coredns-b96499967-c6827                   1/1     Running     0             30m    10.42.1.124   ip-172-31-34-0    <none>           <none>
traefik-7cd4fcff68-f8b7z                  1/1     Running     0             5m7s   10.42.0.20    ip-172-31-46-55   <none>           <none>
traefik-7cd4fcff68-pftq7                  1/1     Running     0             5m7s   10.42.2.107   ip-172-31-41-97   <none>           <none>
traefik-7cd4fcff68-l6t45                  1/1     Running     0             5m7s   10.42.1.125   ip-172-31-34-0    <none>           <none>

chilly-telephone-51989

12/11/2022, 6:25 AM

please note that this cluster is k3s, 1 master 2 agents. all pods are running on two agent nodes. This is on Amazon server. registry for docker is running on master 1. the problem happened when the master was rebooted. the code system is ubuntu 20.10 LTS. all we are getting is 504 gateway timed out whether you access from over the net or private IP of master 1

worried-judge-39444

02/11/2023, 11:55 AM

Old IPTables versions? https://docs.k3s.io/advanced#raspberry-pi https://github.com/k3s-io/k3s/issues/3117

333 Views

Open in Slack

Previous Next