Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service unavailable #254

Closed
iluwatar opened this issue May 19, 2023 · 3 comments
Closed

Service unavailable #254

iluwatar opened this issue May 19, 2023 · 3 comments
Labels
bug Something isn't working needs investigation

Comments

@iluwatar
Copy link

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?

@liwenwu-amazon
Copy link
Contributor

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?

@iluwatar
Copy link
Author

Recreated the cluster from scratch and got it working. Thanks for help!

@iluwatar
Copy link
Author

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.

@iluwatar iluwatar reopened this May 23, 2023
@solmonk solmonk added bug Something isn't working needs investigation labels Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs investigation
Projects
None yet
Development

No branches or pull requests

3 participants