failed_eds_healthissues between a sidecar and a service in another data center using Meshgate WAN federation.
upstream connect error or disconnect/reset before headers. reset reason: connection termination: 0when using consul connect. Is there a workaround for this? I see that Envoy has an option to retry on reset connections. Is that configurable in Consul?
HTTP Maximum Connections per Client-
http_max_conns_per_client. Looking to hotfix some servers and id like to confirm the configuration has been taken but I can’t seem to figure out how to list the config for that entry (if at all possible). Thank you in advance
Try to run a
consul reload -token=<token> and get back a
Configuration reload triggered but I don’t see any logs that suggest a reload actually took place, and the value we are attempting to reload
http_max_conns_per_client doesn’t appear to actually have been updated.
consul connectway of starting envoy. What should be the correct way to accomplish this? We are currently using systemctl to manage envoy. Can we configure some thing there for hot restart?
I am running Consul servers on ECS EC2 which all connect up fine via
retry-join on an NLB.
For the clients, I am using ECS Fargate and
retry-join with the aws tags.
The clients seem to find the server instances and their IPv4 address and attempt to join them, but there's no error logged about that failing. What happens is is that the client starts logging logs like:
2022-06-20T09:00:54.961Z [WARN] agent.router.manager: No servers available and
2022-06-20T09:00:54.961Z [ERROR] agent: failed to sync changes: error="No known Consul servers".
I've seen a couple issues about the logs above in GitHub but no solutions and I can't determine if this is even related.
Has anyone seen this before/know off the top of their head what this could be?