I have a running AWS EKS cluster with 2 worker nodes of type T2 and M3. I have mongo deployed on M3 and my application code deployed on T2. If kube-dns pod is running on M3, then microservices don’t talk to mongo, but if it runs on T2, microservices can talk to mongo. How to work on this problem?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Is AWS EKS Windows Ready For Production? (and recent DNS issues) | 2 | 1098 | April 29, 2022 | |
| Microk8's three node HA cluster, odd intermittent issue with coreDNS and Pod to Pod communications | 0 | 29 | August 28, 2025 | |
| DNS not resolving inside a pod | 1 | 6624 | February 16, 2021 | |
| Kubelet does not have ClusterDNS IP configured and cannot create Pod using "ClusterFirst" policy. Falling back to "Default" policy | 1 | 5435 | June 6, 2019 | |
| DNS resolution fails within the cluster, and it can only resolve the Pods deployed on the same host | 1 | 199 | May 29, 2024 |