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
Either update DNS record or /etc/hosts with emissary-ingress LB address
export DGRAPH_HOSTNAME_HTTP="dgraph.local"export SERVICE_IP=$(kubectl get svc emissary-ingress \ --namespace emissary \ --output jsonpath='{.status.loadBalancer.ingress[0].ip}')
sudo sh -c "echo ${SERVICE_IP}${DGRAPH_HOSTNAME_HTTP} >> /etc/hosts"
Attempt to reach the address
curl -siv dgraph.local/state
Expected behavior
I would expect when accessing the endpoint using the hostname, e.g. dgraph.local, that I would get a response from the server. This means that emissary-ingress would scan for the ingress resource, make the appropriate configurations, and communicate this in the logs. But not of these seems to be happening.
When I try to configure something similar using Listerner, Host, and Mapping, this works fine.
Versions (please complete the following information):
Describe the bug
The ingress resource is not functional it seems, emissary-ingress does not capture any changes needed. If there are any other requirements outside of the ingress, it is not documented at https://www.getambassador.io/docs/emissary/latest/topics/running/ingress-controller#when-and-how-to-use-the-ingress-resource
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect when accessing the endpoint using the hostname, e.g.
dgraph.local
, that I would get a response from the server. This means that emissary-ingress would scan for the ingress resource, make the appropriate configurations, and communicate this in the logs. But not of these seems to be happening.When I try to configure something similar using Listerner, Host, and Mapping, this works fine.
Versions (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: