Kubernetes ingress rule not working about kubernetes-ingress-controller

[yorinasub17]

I came across this as well, and noticed that the ingress controller ignores any ingress rules that don't have a specific hostname attached to it. It worked once I specified a host to the ingress rule.

[angapov]

Same behavior with same manifests on minikube.

[angapov]

It seems that ingress-controller is not doing anything. I see no POST requests in admin-api and database tables are also empty.

[devdavidkarlsson]

kubernetes.io/ingress.class: "kong"

should be

kubernetes.io/ingress.class: "nginx"

export KONG_ADMIN_PORT=$(minikube service -n kong kong-ingress-controller --url --format "{{ .Port }}")
export KONG_ADMIN_IP=$(minikube service   -n kong kong-ingress-controller --url --format "{{ .IP }}")
export PROXY_IP=$(minikube   service -n kong kong-proxy --url --format "{{ .IP }}" | head -1)
export HTTP_PORT=$(minikube  service -n kong kong-proxy --url --format "{{ .Port }}" | head -1)
export HTTPS_PORT=$(minikube service -n kong kong-proxy --url --format "{{ .Port }}" | tail -1)
curl ${KONG_ADMIN_IP}:${KONG_ADMIN_PORT}/routes |jq .
curl ${KONG_ADMIN_IP}:${KONG_ADMIN_PORT}/services |jq .

[angapov]

But I specified --ingress-class=kong in ingress-controller args...

[devdavidkarlsson]

Hmm, ok. What do you get on the endpoints listed above?

And the upstreams one:

curl ${KONG_ADMIN_IP}:${KONG_ADMIN_PORT}/upstreams |jq .

[angapov]

@yorinasub17 you are right. Configuring hosts did the trick. Thank you!