You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My problem appears in step "check service connectivity". When I exec into the pods and try to call the service using the curl command, e.g. curl -v inventory-aws-application-ne-03449e711929f70b4.7d67968.vpc-lattice-svcs.eu-west-1.on.aws, it always responds with 503 service not available.
Any ideas how to debug what is going wrong?
The text was updated successfully, but these errors were encountered:
You may want to double check if security group is configured correctly. Can you check the flowlog and see if anything is dropped due to security group?
Found out what was the root cause. If the EKS cluster has the VPC CNI plugin installed, it results in Service not Available when checking service connectivity.
Hi,
I followed the deployment steps at https://www.gateway-api-controller.eks.aws.dev/deploy/
Next, I tried to set up the single cluster/VPC service-to-service communications as indicated here: https://www.gateway-api-controller.eks.aws.dev/getstarted/
My problem appears in step "check service connectivity". When I exec into the pods and try to call the service using the curl command, e.g. curl -v inventory-aws-application-ne-03449e711929f70b4.7d67968.vpc-lattice-svcs.eu-west-1.on.aws, it always responds with 503 service not available.
Any ideas how to debug what is going wrong?
The text was updated successfully, but these errors were encountered: