Pankaj Arora:
Team, In the lab Ingress Networking - 1, there is no endpoint configured as Default backend in “Ingress Resource” on Question 12; but still if I am not appending the /wear or /watch in the URL; I am being redirected to “404 page - we are not there but we are working on it”.
Here in this scenario, I want to understand from where this 404 page is coming when there is not Default backend endpoint configured in Ingress Resource.
controlplane $ kubectl describe ingress ingress-wear-watch -n=app-space
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use <http://networking.k8s.io/v1|networking.k8s.io/v1> Ingress
Name: ingress-wear-watch
Namespace: app-space
Address:
Default backend: default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
Rules:
Host Path Backends
---- ---- --------
*
/wear wear-service:8080 10.244.1.2:8080)
/watch video-service:8080 10.244.1.3:8080)
Annotations: <http://nginx.ingress.kubernetes.io/rewrite-target|nginx.ingress.kubernetes.io/rewrite-target>: /
<http://nginx.ingress.kubernetes.io/ssl-redirect|nginx.ingress.kubernetes.io/ssl-redirect>: false
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal CREATE 10m nginx-ingress-controller Ingress app-space/ingress-wear-watch
Normal UPDATE 10m nginx-ingress-controller Ingress app-space/ingress-wear-watch
Still getting this page (below pasted screenshot):
