-
Notifications
You must be signed in to change notification settings - Fork 397
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
[BUG] ColorGateway connection refused #142
Comments
I have repeated the entire set of instructions using us-east-2 and still get the same error. Here is the full output
|
Can you confirm if the following works?
|
You may see errors due to any of the following. But these errors should go away once the configurations is distributed.
I noticed a different behavior that maps to (2) and (3)
|
I appear to be having the same problem (also in I can
|
Here you go.
|
After not touching this for 6 days it appears the problem resolved itself for me. I am now able to curl the color gateway from inside the cluster.
Next time I see an error I'll enable debug logging on the gateway sidecar and see if I see anything in the logs. For anyone else that also needs to do this:
Change the APPMESH_LOG_LEVEL environment variable on the container spec from |
Please reopen if you see any more issues. Thanks |
@kiranmeduri I am also getting this error.
|
The logs from the color-gateway envoy container:
|
@jicowan Envoy seems to removing app clusters: Can you paste the logs for your |
Describe the bug
Following https://github.com/aws/aws-app-mesh-examples/blob/master/walkthroughs/eks/base.md
I am unable to perform the curl command from curler to the gateway due to a connection refused error.
I am using
us-west-2
Platform
EKS
To Reproduce
I have executed the steps on the walkthrough.
Expected behavior
I expect the curl command to comeback with OK.
The current curl command response is as follows:
Config files, and API responses
API Gateway Envoy Logs:
The text was updated successfully, but these errors were encountered: