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

improves text format for readability (#7855)

Browse source 
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.
This commit is contained in:
Jessica Andersson 2021-10-27 15:31:26 +02:00 committed by GitHub
parent 987a721723
commit 4da87d128d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/index.md
View file

@ -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: