This message was deleted.
# k3sa
adamant-kite-43734
07/25/2023, 12:26 PMThis message was deleted.
✅ 1
c
chilly-telephone-51989
07/25/2023, 12:40 PMthis is the nslookup output
Copy code
# nslookup postgres.xplorie ;; communications error to 10.43.0.10#53: timed out ;; communications error to 10.43.0.10#53: timed out ;; communications error to 10.43.0.10#53: timed out ;; no servers could be reachedchilly-telephone-51989
07/25/2023, 12:47 PMI deleted the coreDNS pod, then scaled them to 3 (as I have 3 node cluster). My master node is tainted so I'm not sure if it would be able to run the pod there for CoreDNS.
after this i tried nslookup and this is what I got
Copy code
root@connections-6c894cb57-5wvdf:/app# nslookup mongo.xplorie
Server: 10.43.0.10
Address: 10.43.0.10#53
mongo.xplorie.svc.cluster.local canonical name = <http://explorie-mongodb-cluste.mongodb.net|explorie-mongodb-cluste.mongodb.net>.
;; communications error to 10.43.0.10#53: timed out
;; communications error to 10.43.0.10#53: timed out
;; communications error to 10.43.0.10#53: timed out
;; no servers could be reachedc
creamy-pencil-82913
07/25/2023, 5:12 PMSounds like traffic between pods on different nodes is being dropped. Are you sure that you’ve opened the correct ports for vxlan traffic between nodes?
c
chilly-telephone-51989
07/25/2023, 5:17 PMi think so. if there are any specific verification you need, let me know please
c
creamy-pencil-82913
07/25/2023, 5:19 PMcheck the ports listed here https://docs.k3s.io/installation/requirements#inbound-rules-for-k3s-server-nodes
c
chilly-telephone-51989
07/25/2023, 5:46 PMthese ports are open in the security group on AWS for 3 nodes
chilly-telephone-51989
07/25/2023, 5:58 PMupdate: some ports are blocked.
TCP 2379 - 2380
UDP 8472
UDP 51820
UDP 51821
c
creamy-pencil-82913
07/25/2023, 6:13 PMwell that would do it
c
chilly-telephone-51989
07/26/2023, 5:20 AM@creamy-pencil-82913 the ports are open and everything seems to be working fine now.
thanks a lot for always helping me out !
✅ 1
40 Views