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
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-gateway
pointing theCONSUL_HTTP_ADDR
to the dc2 cluster addressdc1 - agent configuration
dc1 - ingress-gateway configuration
dc2 - agent configuration
dc2 - ingress-gateway configuration
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 SMP
dc2:
1.8.5
#25~18.04.1-Ubuntu SMP
Agents
dc1
1.8.4
COS GKE
v1.15.12-gke.20
dc2
1.8.4
COS GKE
v1.15.12-gke.20
Ingress Gateways
dc1
1.8.5
923c4111bb48405ac96ef050c4f59ebbad3d7761/1.14.4/Clean/RELEASE/BoringSSL
dc2
1.8.5
923c4111bb48405ac96ef050c4f59ebbad3d7761/1.14.4/Clean/RELEASE/BoringSSL
Log Fragments
Server logs
dc1
dc2
The text was updated successfully, but these errors were encountered: