Unable to Connect to Exported Service Across AWS EKS Clusters Using WireGuard Cable Driver

[Parth Godase]

Hi Team,

I am encountering an issue with Submariner when attempting to connect to an exported service across two AWS EKS clusters using the WireGuard cable driver. Despite following the configuration steps and achieving a Connected status in Submariner diagnostics, I cannot access the exported service from the remote cluster.

Setup Details

• Clusters:

  • us-east-1: Cluster where the broker is deployed.
  • ap-northeast-3: Remote cluster joined to the broker.

• Submariner Version: 0.19.2

• CNI Plugin: Detected as "generic" on both clusters.

Cluster Details:

• us-east-1:

  • Service CIDR: 10.200.0.0/16
  • Cluster CIDR: 192.168.0.0/18

• ap-northeast-3:

  • Service CIDR: 10.100.0.0/16
  • Cluster CIDR: 172.32.128.0/17

Steps to Reproduce

1. On Cluster in us-east-1:

   • Deployed an nginx pod in the demo namespace.
   • Exposed the deployment as a service on port 80.
   • Exported the service using subctl export service.

2. On Cluster in ap-northeast-3:

   • Created the demo namespace.
   • Verified that the exported service (nginx) is visible in the cluster.
   • Used nslookup to confirm the DNS translation of the service to the correct ClustersetIP (10.200.29.110).
   • Deployed a test pod (tmp-shell) and attempted to curl the exported service (nginx.demo.svc.clusterset.local).
3. Observed Behavior
   • The curl command results in a timeout error:
     curl: (28) Failed to connect to nginx.demo.svc.clusterset.local port 80: Operation timed out
   • nslookup resolves the service name to the correct ClustersetIP address (10.200.29.110).
   • Submariner diagnostics (subctl diagnose all and subctl show all) show no errors, and the connection between clusters is reported as Connected.

Request

Please help identify why the service is not accessible across clusters despite the diagnostics indicating a healthy Submariner setup. Let me know if additional logs or information are needed to troubleshoot the issue.

Thank you!
Parth