Consul Ingress-Gateway doesn't pick the configuration from a federated cluster #9201
Labels
theme/connect
Anything related to Consul Connect, Service Mesh, Side Car Proxies
theme/federation-usability
Anything related to Federation
theme/ingress-gw
Track ingress work
Comments
jsosulska
added
theme/connect
|
i think the improvement in #9320 would provide greater visibility into what i'd guess is actually a replication issue |
|
It does seem to be the same issue @blake. We still didn't update to 1.9.x, but we're also gonna do it |
|
As I'm not using consul with this configuration anymore I can't really say if it's fixed or not and I can't test it. I'm closing the issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview of the Issue
Consul Connect Ingress Gateway doesn't pick up the configuration applied when it's federated
I deployed 2 consul clusters federated (normal federation without the mesh-gateway features) and deployed 2 ingress-gateway, one for each datacenter
Architecture
dc1 - primary_dc, federated cluster
dc2 - federated cluster
consul config list -kind ingress-gatewaypointing theCONSUL_HTTP_ADDRto the dc2 cluster addressdc1 - agent configuration
{ "bind_addr": "<redacted>", "bootstrap_expect": 3, "client_addr": "0.0.0.0", "config_entries": { "bootstrap": [ { "config": { "protocol": "http" }, "kind": "proxy-defaults", "name": "global" } ] }, "connect": { "enabled": true }, "data_dir": "/data/consul-server", "datacenter": "dc1", "dns_config": { "enable_truncate": false }, "domain": "consul.", "enable_central_service_config": true, "http_config": { "response_headers": { "Access-Control-Allow-Headers": "*", "Access-Control-Allow-Methods": "*", "Access-Control-Allow-Origin": "*" } }, "node_name": "<redacted>", "primary_datacenter": "dc1", "retry_join": ["<consul_server_ips>"], "retry_join_wan": ["consul.service.dc2.consul"], "server": true, "translate_wan_addrs": true, "ui": true }dc1 - ingress-gateway configuration
{ "Kind": "ingress-gateway", "Name": "ingress-dc1", "TLS": { "Enabled": false }, "Listeners": [ { "Port": 80, "Protocol": "http", "Services": [ { "Name": "*" } ] } ] }dc2 - agent configuration
{ "bind_addr": "<redacted>", "bootstrap_expect": 3, "client_addr": "0.0.0.0", "config_entries": { "bootstrap": [ { "config": { "protocol": "http" }, "kind": "proxy-defaults", "name": "global" } ] }, "connect": { "enabled": true }, "data_dir": "/data/consul-server", "datacenter": "dc2", "dns_config": { "enable_truncate": false }, "domain": "consul.", "enable_central_service_config": true, "http_config": { "response_headers": { "Access-Control-Allow-Headers": "*", "Access-Control-Allow-Methods": "*", "Access-Control-Allow-Origin": "*" } }, "node_name": "<redacted>", "primary_datacenter": "dc1", "retry_join": ["<consul_internal_ips>"], "retry_join_wan": ["consul.service.dc1.consul"], "server": true, "translate_wan_addrs": true, "ui": true }dc2 - ingress-gateway configuration
{ "Kind": "ingress-gateway", "Name": "ingress-dc2", "TLS": { "Enabled": false }, "Listeners": [ { "Port": 80, "Protocol": "http", "Services": [ { "Name": "*" } ] } ] }dc2 - consul server logs
This is the only log that I see that is referencing ingress-gateway, all the other logs in the consul servers are related to the snapshots that I do
Consul config list results pointing to both consul clusters
Reproduction Steps
Steps to reproduce this issue, eg:
Consul info for both Client and Server
Client info - dc1
Server info - dc1
Client info - dc2
Server info - dc2
Operating system and Environment details
Servers
dc1
1.8.5#24~18.04.1-Ubuntu SMPdc2:
1.8.5#25~18.04.1-Ubuntu SMPAgents
dc1
1.8.4COS GKEv1.15.12-gke.20dc2
1.8.4COS GKEv1.15.12-gke.20Ingress Gateways
dc1
1.8.5923c4111bb48405ac96ef050c4f59ebbad3d7761/1.14.4/Clean/RELEASE/BoringSSLdc2
1.8.5923c4111bb48405ac96ef050c4f59ebbad3d7761/1.14.4/Clean/RELEASE/BoringSSLLog Fragments
Server logs
dc1
dc2
The text was updated successfully, but these errors were encountered: