Difference between revisions of "Ingress-nginx-controller-controller-defaultbackend"
Jump to navigation
Jump to search
(2 intermediate revisions by the same user not shown) | |||
Line 2: | Line 2: | ||
* https://kubernetes.github.io/ingress-nginx/user-guide/default-backend/ | * https://kubernetes.github.io/ingress-nginx/user-guide/default-backend/ | ||
+ | The default backend is a service which handles all URL paths and hosts the Ingress-NGINX controller doesn't understand (i.e., all the requests that are not mapped with an Ingress). | ||
+ | |||
+ | Basically a default backend exposes two URLs: | ||
+ | |||
+ | /healthz that returns 200 | ||
+ | / that returns 404 | ||
+ | |||
+ | == Related == | ||
+ | [[ingress-nginx-controller-controller]] | ||
+ | [[ingress-nginx-controller-controller-admission]] | ||
+ | [[ingress-nginx-controller-controller-defaultbackend]] | ||
== See also == | == See also == | ||
+ | * {{ingress-nginx-controller}} | ||
* {{ingress-nginx}} | * {{ingress-nginx}} | ||
[[Category:K8s]] | [[Category:K8s]] |
Latest revision as of 23:43, 15 February 2024
The default backend is a service which handles all URL paths and hosts the Ingress-NGINX controller doesn't understand (i.e., all the requests that are not mapped with an Ingress). Basically a default backend exposes two URLs: /healthz that returns 200 / that returns 404
Related[edit]
ingress-nginx-controller-controller ingress-nginx-controller-controller-admission ingress-nginx-controller-controller-defaultbackend
See also[edit]
Advertising: