-
Notifications
You must be signed in to change notification settings - Fork 680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ingress no longer functions #5451
Comments
This is also minimal steps using Apache HTTPd # deploy application
kubectl create namespace "ingress-test"
kubectl create deployment httpd \
--image "httpd" \
--replicas 3 \
--port 80 \
--namespace "ingress-test"
# create proxy to deployment
kubectl expose deployment httpd \
--port 80 \
--target-port 80 \
--type ClusterIP \
--namespace "ingress-test"
# provision application load balancer
kubectl create ingress httpd-ingress \
--rule "ingress.test/=httpd:80" \
--annotation "kubernetes.io/ingress.class=ambassador" \
--class "ambassador" \
--namespace "ingress-test"
export SERVICE_IP=$(kubectl get svc emissary-ingress \
--namespace emissary \
--output jsonpath='{.status.loadBalancer.ingress[0].ip}'
)
sudo sh -c "echo ${SERVICE_IP} ingress.test >> /etc/hosts"
curl ingress.test |
cindymullins-dw
added
a:docs
Issue relates to documentation
t:bug
Something isn't working
labels
Dec 1, 2023
I hope someone can look at this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: