-
Notifications
You must be signed in to change notification settings - Fork 33
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] Envoy proxy container failing #39
Comments
Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide and sure to join the community Slack. |
Thank you, @felixfaisal 👍 |
Description: This fixes a previous open issue layer5io#39 Updated envoy.yaml - Envoy now calls for typed_config - Rearranged placement of the filters, but it probably can be reworked to make it cleaner - Clusters is now set up with individual load assignment, no longer uses hosts
Hello I would like to contribute to this. I already started working on this issue, and I have a working |
Description: This fixes a previous open issue layer5io#39 Updated envoy.yaml - Envoy now calls for typed_config - Rearranged placement of the filters, but it probably can be reworked to make it cleaner - Clusters is now set up with individual load assignment, no longer uses hosts
Description: This fixes a previous open issue layer5io#39 Updated envoy.yaml - Envoy now calls for typed_config in `v3` - Rearranged placement of the filters, but it probably can be reworked to make it cleaner - Clusters is now set up with an endpoint, instead of `hosts` - Probably need to fix spacing Signed-off-by: Antonette Caldwell <[email protected]>
Description: This fixes a previous open issue layer5io#39 Updated envoy.yaml - Envoy now calls for typed_config in `v3` - Rearranged placement of the filters, but it probably can be reworked to make it cleaner - Clusters is now set up with an endpoint, instead of `hosts` - Probably need to fix spacing Signed-off-by: Antonette Caldwell <[email protected]>
Description: This fixes a previous open issue layer5io#39 Updated envoy.yaml - Envoy now calls for typed_config in `v3` - Rearranged placement of the filters, but it probably can be reworked to make it cleaner - Clusters is now set up with an endpoint, instead of `hosts` - Probably need to fix spacing Signed-off-by: Antonette Caldwell <[email protected]>
Description: This fixes a previous open issue layer5io#39 Updated envoy.yaml - Envoy now calls for typed_config in `v3` - Rearranged placement of the filters, but it probably can be reworked to make it cleaner - Clusters is now set up with an endpoint, instead of `hosts` - Probably need to fix spacing Signed-off-by: Antonette Caldwell <[email protected]>
Description
Proxy container(Envoy) container exits due to an issue with configuration
Expected Behavior
Should run the TCP metrics succesfully
Error
Environment:
To Reproduce
Follow the steps for TCPmetrics to reproduce this error,
However I've used
make run
to see docker logsThe text was updated successfully, but these errors were encountered: