You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have Consul services registered in a Consul datacenter NOT named dc1 but Ambassador is not resolving endpoints for this service to pass on to Envoy and so the service is not routable.
Describe the bug
We have Consul services registered in a Consul datacenter NOT named
dc1
but Ambassador is not resolving endpoints for this service to pass on to Envoy and so the service is not routable.On the Ambassador Kubernetes service:
On a Kubernetes service:
In
snapshot.yaml
I seebut in
aconf.json
I see:the
datacenter
value has reverted todc1
and I think this is causing the failure to find endpoints.It looks like this code
https://github.com/datawire/ambassador/blob/0e1e8ffbc83f7a96b815ff68ed786b59be09cce3/ambassador/ambassador/config/resourcefetcher.py#L536
is incorrect and
'id'
should be'Id'
as that is the name of the datacenter value insnapshot.yaml
.Versions (please complete the following information):
Additional context
Related:
The text was updated successfully, but these errors were encountered: