rboyer
commented
6 years ago The getting started guide has the proxies and the consul agent run within the same network namespace with the docker flag --network host.
In your example your sidecar proxies and consul agent do not share a network namespace, so the default gRPC server address will need to be explicitly configured like you did with the HTTP api address. The gRPC server serves the xDS protocol for envoy.
In your example you would need to specify -grpc-addr consul:8502 in addition to -http-addr http://consul:8500 like:
-sidecar-for core-demo-api2 -admin-bind 0.0.0.0:19000 -http-addr http://consul:8500 -grpc-addr consul:8502I picked up on the misconfig because I saw that the .configs[0].bootstrap.static_resources.clusters[0].hosts[0].socket_address value in your envoy admin config dump was set to { "address": "127.0.0.1", "port_value": 8502 } instead of the ip address of the consul agent.
mmisztal1980
banks
stale[bot]
ghost
Overview of the Issue
I've created a PoC environment for 2x .NET Core 2.1 Services communicating via Consul-Connect. The entire setup relies on a consul server instance, which uses a services.json file to perform the registrations in a 'static' way. If I understand the process correctly, the sidecar proxies should retrieve their configuration from the consul-server after starting up.
Once the consul server container is healthy, 2x sidecar-proxies start. At this point the entire setup is healthy:
When attempting to have core-demo-api1 call core-demo-api1 , I'm getting a 404 response. I've exposed core-demo-api1-sidecar-proxy 's port 19000 and obtained a config dump in which I do not see any routes defined to core-demo-api2, which I believe is the root cause for the communication issue between the 2 services. I believe I've followed the available documentation to the letter, so my situation can be a potential bug.
Reproduction Steps
consul-envoy/Dockerfile
services.json
docker-compose.yml
docker-compose.override.yml
Consul info for both Client and Server
Client info
**(!) Executed inside one of the sidecar-proxy containers (!)** ``` # consul info Error querying agent: Get http://127.0.0.1:8500/v1/agent/self: dial tcp 127.0.0.1:8500: connect: connection refused ```envoy.yaml
```yaml admin: access_log_path: /tmp/admin_access.log address: socket_address: protocol: TCP address: 127.0.0.1 port_value: 9901 static_resources: listeners: - name: listener_0 address: socket_address: protocol: TCP address: 0.0.0.0 port_value: 10000 filter_chains: - filters: - name: envoy.http_connection_manager config: stat_prefix: ingress_http route_config: name: local_route virtual_hosts: - name: local_service domains: ["*"] routes: - match: prefix: "/" route: host_rewrite: www.google.com cluster: service_google http_filters: - name: envoy.router clusters: - name: service_google connect_timeout: 0.25s type: LOGICAL_DNS # Comment out the following line to test on v6 networks dns_lookup_family: V4_ONLY lb_policy: ROUND_ROBIN hosts: - socket_address: address: google.com port_value: 443 tls_context: { sni: www.google.com } ```Server info
``` # consul info agent: check_monitors = 0 check_ttls = 0 checks = 4 services = 4 build: prerelease = revision = e8757838 version = 1.3.0 consul: bootstrap = true known_datacenters = 1 leader = true leader_addr = 127.0.0.1:8300 server = true raft: applied_index = 1439 commit_index = 1439 fsm_pending = 0 last_contact = 0 last_log_index = 1439 last_log_term = 2 last_snapshot_index = 0 last_snapshot_term = 0 latest_configuration = [{Suffrage:Voter ID:7df0a6a8-3f7a-10f6-d759-e46d1b024aa2 Address:127.0.0.1:8300}] latest_configuration_index = 1 num_peers = 0 protocol_version = 3 protocol_version_max = 3 protocol_version_min = 0 snapshot_version_max = 1 snapshot_version_min = 0 state = Leader term = 2 runtime: arch = amd64 cpu_count = 2 goroutines = 103 max_procs = 2 os = linux version = go1.11.1 serf_lan: coordinate_resets = 0 encrypted = false event_queue = 1 event_time = 2 failed = 0 health_score = 0 intent_queue = 0 left = 0 member_time = 1 members = 1 query_queue = 0 query_time = 1 serf_wan: coordinate_resets = 0 encrypted = false event_queue = 0 event_time = 1 failed = 0 health_score = 0 intent_queue = 0 left = 0 member_time = 1 members = 1 query_queue = 0 query_time = 1 ```Operating system and Environment details
0 Windows 10 Enterprise x64 running Docker for Windows (MobyLinuxVM)
Log Fragments
TBD Include appropriate Client or Server log fragments. If the log is longer than a few dozen lines, please include the URL to the gist of the log instead of posting it in the issue. Use
-log-level=TRACEon the client and server to capture the maximum log detail.