From 666c2bc3da8792feafcf98f472760f0c649c130b Mon Sep 17 00:00:00 2001 From: Ray Huang Date: Fri, 19 Jan 2024 13:05:33 -0500 Subject: [PATCH] Add note to include '-ingress-class-by-name=true' for Multiple Controllers instruction. --- docs/user-guide/multiple-ingress.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/multiple-ingress.md b/docs/user-guide/multiple-ingress.md index 1780f5e4f..54a18fbb9 100644 --- a/docs/user-guide/multiple-ingress.md +++ b/docs/user-guide/multiple-ingress.md @@ -12,7 +12,7 @@ If all ingress controllers respect IngressClasses (e.g. multiple instances of in First, ensure the `--controller-class=` and `--ingress-class` are set to something different on each ingress controller, If your additional ingress controller is to be installed in a namespace, where there is/are one/more-than-one ingress-nginx-controller(s) already installed, then you need to specify a different unique `--election-id` for the new instance of the controller. -In addition, you need to specify `--ingress-class-by-name=true` in the controller args list. The `--ingress-class-by-name` arg defines if Ingress Controller should watch for Ingress Class by Name together with Controller Class. (default false). +In addition, you need to specify `--ingress-class-by-name=true` in the controller args list. The `--ingress-class-by-name` defines if Ingress Controller should watch for Ingress Class by Name together with Controller Class. (default false). ```yaml # ingress-nginx Deployment/Statefulset