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 | |
|---|---|---|---|---|
| EC2 private DNS names do not resolve in the pods | 10 | 5405 | December 14, 2020 | |
| Kubernetes cluster coredns problem | 0 | 445 | May 29, 2024 | |
| Shared DNS between two Kubernetes Clusters | 0 | 654 | June 6, 2020 | |
| Should coredns pods be running on worker nodes? | 1 | 4119 | December 23, 2021 | |
| K8s local on-premise setup not able to resolve dns name | 1 | 123 | October 15, 2024 |