From 66cbd577551dc4ee0b3319bf850270d8f460d0ba Mon Sep 17 00:00:00 2001 From: Ray Huang Date: Fri, 19 Jan 2024 16:04:14 -0500 Subject: [PATCH] Improve docs for multiple instances of controller on one cluster (#10882) * Added note to include '--ingress-class-by-name=true' for Multiple Ingress controllers instruction. * Add note to include '-ingress-class-by-name=true' for Multiple Controllers instruction. --- docs/user-guide/multiple-ingress.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/user-guide/multiple-ingress.md b/docs/user-guide/multiple-ingress.md index 5c1e26c7cd..54a18fbb94 100644 --- a/docs/user-guide/multiple-ingress.md +++ b/docs/user-guide/multiple-ingress.md @@ -10,7 +10,9 @@ But, when user has deployed with `scope.enabled`, then the ingress class resourc If all ingress controllers respect IngressClasses (e.g. multiple instances of ingress-nginx v1.0), you can deploy two Ingress controllers by granting them control over two different IngressClasses, then selecting one of the two IngressClasses with `ingressClassName`. -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. +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` defines if Ingress Controller should watch for Ingress Class by Name together with Controller Class. (default false). ```yaml # ingress-nginx Deployment/Statefulset @@ -24,6 +26,7 @@ spec: - '--election-id=ingress-controller-leader' - '--controller-class=k8s.io/internal-ingress-nginx' - '--ingress-class=internal-nginx' + - '--ingress-class-by-name=true' ... ```