From 4b317389e66dbe0177e7cdc17e4aff50ebcb47da Mon Sep 17 00:00:00 2001 From: Eric Stokes Date: Sat, 15 Feb 2020 08:33:42 +0000 Subject: [PATCH] Fixed incorrect cli flag --default-backend The flag stated in the example readme is `--default-backend` but passing that (or looking at --help`) for the ingress controller shows: unknown flag: --default-backend ... --default-backend-service string Service used to serve HTTP requests not matching any known server name (catch-all). Takes the form "namespace/name". The controller configures NGINX to forward requests to the first port of this Service. ref: https://github.com/kubernetes/ingress-nginx/blob/master/cmd/nginx/flags.go#L55 --- docs/examples/customization/custom-errors/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/examples/customization/custom-errors/README.md b/docs/examples/customization/custom-errors/README.md index a6a1d5aca..6ced0d7cd 100644 --- a/docs/examples/customization/custom-errors/README.md +++ b/docs/examples/customization/custom-errors/README.md @@ -28,7 +28,7 @@ service/nginx-errors ClusterIP 10.0.0.12 80/TCP 10s If you do not already have an instance of the NGINX Ingress controller running, deploy it according to the [deployment guide][deploy], then follow these steps: -1. Edit the `nginx-ingress-controller` Deployment and set the value of the `--default-backend` flag to the name of the +1. Edit the `nginx-ingress-controller` Deployment and set the value of the `--default-backend-service` flag to the name of the newly created error backend. 2. Edit the `nginx-configuration` ConfigMap and create the key `custom-http-errors` with a value of `404,503`.