- Newest
- Most votes
- Most comments
It's possible that the issue is related to DNS resolution or routing. When you try to access the K8s service from a EC2 instance in VPC B using the endpoint 10.0.102.250:80, the request is being sent to the IP address, but it's not reaching the service.
Since you can ping the worker node's IP address 10.0.100.200 from the EC2 instance in VPC B, it seems that routing between the VPCs is working correctly. However, if you're not able to access the K8s service, it could be due to a DNS resolution issue.
When you run tracert 10.0.102.250 from the EC2 instance in VPC B, it shows the hostname ip-10-0-102-240.us-west-2.compute.internal. This hostname is likely being resolved by a DNS server in VPC A, and it's possible that the DNS resolution is not working correctly from VPC B.
To troubleshoot the issue, you could try to manually resolve the hostname ip-10-0-102-240.us-west-2.compute.internal to the IP address 10.0.102.250 from the EC2 instance in VPC B using the nslookup command. If the DNS resolution is not working correctly, you could try to update the DNS configuration in VPC B to use the same DNS server as VPC A or configure a DNS resolver that can resolve the hostname correctly.
Additionally, you could try to access the K8s service using the IP address 10.0.100.200 instead of the endpoint 10.0.102.250:80 to see if it works. If it does, then the issue is likely related to DNS resolution, and you may need to update the DNS configuration in VPC B.
Ref links: https://docs.aws.amazon.com/vpc/latest/userguide/vpc-dns.html#vpc-dns-troubleshooting https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting.html#service-load-balancer-issues
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago