- Newest
- Most votes
- Most comments
Hi,
Yes, you can, but if in a different namespace, you might need to add a namespace as well: http://serviceAname.namespaceName.svc.cluster.local:portnum
Please take a look at this documentation https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/
Hi,
Yes, using the service name directly is the most easier way. This is one of the simplest ways of addressing, but it requires cluster DNS to be set-up and working properly. Pods that run inside the Amazon EKS cluster use the CoreDNS service's cluster IP as the default name server for querying internal and external DNS records. If there are issues with the CoreDNS pods, service configuration, or connectivity, then applications can fail DNS resolutions. If you are facing or face any issues with name resolutions you can refer to this post for guidance - https://repost.aws/knowledge-center/eks-dns-failure
Relevant content
- Accepted Answerasked 7 months ago
- Accepted Answerasked 9 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 22 days ago
- AWS OFFICIALUpdated a year ago