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

docs: fix inconsistent controller annotation (#8196)

Browse source 
The annotation for the controller class was inconsistent in the example. From my best understanding, I have tried to fix the inconsistency.

Also, removed an incomplete sentence. And made one sentence more clear by breaking it up.
This commit is contained in:
Sandip Bhattacharya 2022-01-27 04:06:50 +01:00 committed by GitHub
parent 53ac0ddd42
commit 6eecefd3da
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/user-guide/multiple-ingress.md
View file

@ -2,12 +2,11 @@
By default, deploying multiple Ingress controllers (e.g., `ingress-nginx` & `gce`) will result in all controllers simultaneously racing to update Ingress status fields in confusing ways. By default, deploying multiple Ingress controllers (e.g., `ingress-nginx` & `gce`) will result in all controllers simultaneously racing to update Ingress status fields in confusing ways.
To fix this problem, use [IngressClasses](https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class), the `kubernetes.io/ingress.class` annotation is deprecated from kubernetes v1.22+. To fix this problem, use [IngressClasses](https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class). The `kubernetes.io/ingress.class` annotation is deprecated from kubernetes v1.22+.
## Using IngressClasses ## Using IngressClasses
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`. 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`.
When two or more
First, ensure the `--controller-class=` and `--ingress-class` are set to something different on each ingress controller: First, ensure the `--controller-class=` and `--ingress-class` are set to something different on each ingress controller:
@ -20,7 +19,7 @@ spec:
- name: ingress-nginx-internal-controller - name: ingress-nginx-internal-controller
args: args:
- /nginx-ingress-controller - /nginx-ingress-controller
- '--controller-class=k8s.io/internal-nginx' - '--controller-class=k8s.io/internal-ingress-nginx'
- '--ingress-class=k8s.io/internal-nginx' - '--ingress-class=k8s.io/internal-nginx'
... ...
``` ```