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

Fix documentation format

Browse source
This commit is contained in:
Manuel de Brito Fontes 2018-08-30 15:24:56 -03:00 • committed by Manuel Alejandro de Brito Fontes
parent be0fdc620f
commit f5dda5fecc
No known key found for this signature in database
GPG key ID: 786136016A8BA02A
11 changed files with 25 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -49,10 +49,9 @@ spec:
- '--configmap=ingress/nginx-ingress-internal-controller'
```
## !!! important
!!! important
Deploying multiple Ingress controllers, of different types (e.g., `ingress-nginx` & `gce`), and not specifying a class annotation will
result in both or all controllers fighting to satisfy the Ingress, and all of them racing to update Ingress status field in confusing ways.
Deploying multiple Ingress controllers, of different types (e.g., `ingress-nginx` & `gce`), and not specifying a class annotation will
result in both or all controllers fighting to satisfy the Ingress, and all of them racing to update Ingress status field in confusing ways.
When running multiple ingress-nginx controllers, it will only process an unset class annotation if one of the controllers uses the default
`--ingress-class` value (see `IsValid` method in `internal/ingress/annotations/class/main.go`), otherwise the class annotation become required.
When running multiple ingress-nginx controllers, it will only process an unset class annotation if one of the controllers uses the default
`--ingress-class` value (see `IsValid` method in `internal/ingress/annotations/class/main.go`), otherwise the class annotation become required.