From 4da87d128d834f5dc9dff8b96cc874a4e98a8dc9 Mon Sep 17 00:00:00 2001 From: Jessica Andersson Date: Wed, 27 Oct 2021 15:31:26 +0200 Subject: [PATCH] improves text format for readability (#7855) Small text format changes to section "I have more than one controller running in my cluster, and I want to use the new spec?" to allow for better readability. --- docs/index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/index.md b/docs/index.md index 1154ba32b..6aa2ea81c 100644 --- a/docs/index.md +++ b/docs/index.md @@ -154,10 +154,12 @@ In this scenario, you need to create multiple ingressClasses (see example one). - Ingress-Nginx-IngressClass-1 with .spec.controller equals to "k8s.io/ingress-nginx1" - Ingress-Nginx-IngressClass-2 with .spec.controller equals to "k8s.io/ingress-nginx2" + When deploying your ingress controllers, you will have to change the `--controller-class` field as follows: -Ingress-Nginx-Controller-nginx1 with `k8s.io/ingress-nginx1` -Ingress-Nginx-Controller-nginx2 with `k8s.io/ingress-nginx2` +- Ingress-Nginx-Controller-nginx1 with `k8s.io/ingress-nginx1` +- Ingress-Nginx-Controller-nginx2 with `k8s.io/ingress-nginx2` + Then, when you create an Ingress Object with IngressClassName = `ingress-nginx2`, it will look for controllers with `controller-class=k8s.io/ingress-nginx2` and as `Ingress-Nginx-Controller-nginx2` is watching objects that points to `ingressClass="k8s.io/ingress-nginx2`, it will serve that object, while `Ingress-Nginx-Controller-nginx1` will ignore the ingress object. Bear in mind that, if your `Ingress-Nginx-Controller-nginx2` is started with the flag `--watch-ingress-without-class=true`, then it will serve: