DNS problem for k3s multicloud cluster #10897
allnightlong
started this conversation in
General
Replies: 1 comment
-
is coredns up and running in kube-system namespace ? example kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
coredns-576bfc4dc7-w7q9r 1/1 Running 0 21d
local-path-provisioner-6795b5f9d8-8kvxb 1/1 Running 0 21d
metrics-server-557ff575fb-cqh58 1/1 Running 0 21d if no , first you should check why it does not work , if yes then get the core dns service IP and test it kubectl get svc -n kube-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kube-dns ClusterIP 10.13.0.10 <none> 53/UDP,53/TCP,9153/TCP 21d
metrics-server ClusterIP 10.13.202.13 <none> 443/TCP 21d test dig one.com @10.13.0.10 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I building my cluster with nodes from different datacenters. Actually, the cluster has lived in one dc for some time with 5 node (1 server + 4 agents). Now I'm adding new node in different dc.
Using this tutorial as an example https://docs.k3s.io/networking/distributed-multicloud#embedded-k3s-multicloud-solution
For server:
For agent:
The problem is non of the agent's pod can resolve any hostname. I'm using official dns resolution guide https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/ and
nslookup
is failing both for internal and external requests.Internal:
External:
External with cloudflare's dns:
What could be the problem of this DNS issue? How could I resolve it?
P.S. I'm using k3s version
v1.30.4+k3s1
(latest at the time of writing) both for server and agents.Beta Was this translation helpful? Give feedback.
All reactions