404 handler code

[kfox1111]

currently the 404 handler does just that. only serve out 404 messages (file not found). This is probably the appropriate message to return when a vhost does not exist.

On the other hand, if all of a services members are completely down, 404 is probably not the right answer, as its not that the files are missing so stop trying, but that 503 the server is currently unavailable. keep trying.

Can the 404 handler have a configuration flag added to it to configure which error code to return, so 2 of them can be launched, one for 404 and one for 503?

[aledbf]

@kfox1111 if there are no endpoints available you should see 503, not 404
Please check

ingress-nginx/rootfs/etc/nginx/template/nginx.tmpl

Line 880 in 41cefeb

{{/* if we are sending the request to a custom default backend, we add the required headers */}}

If you use a custom backend you receive the status code and you can customize the action

[kfox1111]

Thanks for the info.

I'm trying to implement this, but getting stuck. Where is the image for this?

docker pull quay.io/kubernetes-ingress-controller/custom-error-pages
Trying to pull repository quay.io/kubernetes-ingress-controller/custom-error-pages ... 
Pulling repository quay.io/kubernetes-ingress-controller/custom-error-pages
Error: Status 403 trying to pull repository kubernetes-ingress-controller/custom-error-pages: "{\"error\": \"Permission Denied\"}"

If I understand right, each ingress object needs an nginx.ingress.kubernetes.io/default-backend set to the custom handler?

[aledbf]

@kfox1111 here https://github.com/kubernetes/ingress-nginx/tree/master/images/custom-error-pages

[kfox1111]

So, do we need to build our own images?

[aledbf]

@kfox1111 no need. Please check https://quay.io/repository/kubernetes-ingress-controller/custom-error-pages-amd64?tab=tags

Edit: #2289

[kfox1111]

Ah. perfect. thanks.

[aledbf]

Closing. Please reopen if you have more questions