DevFW-CICD/ingress-nginx-helm
14
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

make usage more clear about default-backend annotation

Browse source
This commit is contained in:
Tyler Horvath 2019-01-26 11:47:16 -07:00
parent 6618b3987c
commit 6824c78c1b
No known key found for this signature in database
GPG key ID: 63B3E810C328F9DC
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/user-guide/nginx-configuration/annotations.md
View file

@ -247,7 +247,7 @@ nginx.ingress.kubernetes.io/configuration-snippet: |
The ingress controller requires a [default backend](../default-backend.md). The ingress controller requires a [default backend](../default-backend.md).
This service handles the response when the service in the Ingress rule does not have endpoints. This service handles the response when the service in the Ingress rule does not have endpoints.
This is a global configuration for the ingress controller. In some cases could be required to return a custom content or format. In this scenario we can use the annotation `nginx.ingress.kubernetes.io/default-backend: <svc name>` to specify a custom default backend. This is a global configuration for the ingress controller. In some cases could be required to return a custom content or format. In this scenario we can use the annotation `nginx.ingress.kubernetes.io/default-backend: <svc name>` to specify a custom default backend. This `<svc name>` is a reference to a service inside of the same namespace in which you are applying this annotation.
### Custom HTTP Errors ### Custom HTTP Errors